Conversation
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Grammar: “We're understand the problem” should be “We understand the problem” (or similar).
There was a problem hiding this comment.
Typo: “well never” should be “will never”.
There was a problem hiding this comment.
Typo: “Bunder version” should be “Bundler version”.
There was a problem hiding this comment.
Grammar: “One of the those changes” should be “One of those changes”.
| Yesterday I released Bundler 2.0 that introduced a number of breaking changes. One of those changes was setting Bundler to require RubyGems v3.0.0. After making the release, it has become clear that lots of our users are running into issues with Bundler 2 requiring a really new version of RubyGems. |
There was a problem hiding this comment.
Spelling: “exited” should be “excited”.
| on bundler 1.12 and 2.0 _at this very moment_, and are incredibly excited to get |
There was a problem hiding this comment.
Spelling: “offical” should be “official”.
| This release focuses on removing official support of versions of Ruby and RubyGems that have reached their end of life, with a few other small breaking changes. |
There was a problem hiding this comment.
In URL terminology this should be “scheme”, not “schema” (e.g. “https scheme”).
Fixed url like
https://blog.rubygems.org/2013/10/12/goodbye-bundler-14-hello-bundler-15.html.html.