ci: Revert Bundler 4.0.6 pin and use rubygems: latest#306
Merged
Conversation
Bundler 4.0.12 (https://blog.rubygems.org/2026/05/20/4.0.12-released.html) includes ruby/rubygems#9544, which fixes the multi-gemspec git source resolver regression tracked in ruby/rubygems#9536 — the bug that PR rsim#290 worked around by pinning Bundler to 4.0.6 in the RuboCop workflow. - Drop the BUNDLER_VERSION env var and the "Pin Bundler to 4.0.6" step from rubocop.yml; the workaround is no longer needed. - Add `rubygems: latest` to the workflows that exercise modern CRuby (rubocop, test, test_11g, test_11g_ojdbc11), matching the pattern release.yml already uses, so CI resolves Bundler 4.0.12 instead of whatever ships in the setup-ruby tarball. setup-ruby handles JRuby via `gem update --system`, so JRuby matrix entries are safe. ruby_head.yml and jruby_head.yml are intentionally left alone — per setup-ruby docs, head builds are not updated. truffleruby.yml and test_gemfiles.yml are also untouched (TruffleRuby compatibility, and test_gemfiles targets Ruby 2.4–3.3 which cannot install RubyGems 4.x). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
BUNDLER_VERSION: 4.0.6env and the "Pin Bundler to 4.0.6" step from.github/workflows/rubocop.yml.rubygems: latestto the modern-CRuby workflows (rubocop.yml,test.yml,test_11g.yml,test_11g_ojdbc11.yml), matching the pattern already used inrelease.yml, so CI actually picks up Bundler 4.0.12 instead of whatever ships in theruby/setup-ruby@v1tarball.Scope notes
ruby_head.yml,jruby_head.yml: untouched — per setup-ruby docs, "Ruby head/master builds will not be updated" byrubygems: latest.truffleruby.yml: untouched — setup-ruby would attemptgem update --systemon TruffleRuby, which is not reliably supported there.test_gemfiles.yml: untouched — its matrix targets Ruby 2.4 through 3.3, none of which support RubyGems 4.x.test.yml/test_11g.yml/test_11g_ojdbc11.yml: covered — setup-ruby explicitly handles JRuby withgem update --systemforrubygems: latest.Test plan
RuboCopworkflow run completes green; thePin Bundlerstep is gone andSet up Ruby 4.0logs Bundler 4.0.12.testworkflow run completes green for all matrix entries (4.0,3.4,3.3,jruby-10.1.0.0).test_11gandtest_11g_ojdbc11workflows run green.ruby_head,jruby_head,truffleruby) that were intentionally left unchanged.🤖 Generated with Claude Code