Add workaround for Ruby 3.1 after RubyGems 3.7.0 release #780
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Uggh, apparently on Windows Bundler is installed with |
It was originally added by ruby#253, in order to fix CI. However, now CI passes without it so I assume this was fixed by rubyinstaller2. Force actually bypasses dependency constraints so it's actually installing the latest Bundler in a version of Ruby that's incompatible with it.
deivid-rodriguez
force-pushed
the
catchup-with-rubygems-release
branch
from
48a7ec3 to
9142f40
Compare
|
Not using the |
eregon
approved these changes
Jul 16, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Like every time I release a version of RubyGems dropping support for a EOL Ruby, I forgot to update
ruby/setup-rubybefore the release, so thatrubygems: latestdoes not break 😅Fixing it now.
This issue was fixed by rubygems/rubygems#7334, shipped with RubyGems 3.5.4. That version of RubyGems comes by default with Ruby 3.3.1 or higher, so I believe we just need one more future update similar to this one right before shipping a RubyGems version dropping support for Ruby 3.2. I will try to remember that one last time!