ci: Pin Bundler to 4.0.6 in RuboCop workflow as workaround for ruby/rubygems#9536#290
Merged
Merged
Conversation
…ubygems#9536 The RuboCop workflow started failing on master at 2026-05-12T01:01 UTC with: Could not find compatible versions against the multi-gemspec git source `rails/rails` whose top-level gem is in a filtered-out group when `BUNDLE_ONLY=rubocop bundle install` runs under Ruby 4.0.4 (Bundler 4.0.11). The regression is tracked in ruby/rubygems#9536; Bundler 4.0.5 and 4.0.6 succeed while 4.0.7+ fail. Pin Bundler explicitly so the workflow keeps rolling on `ruby-version: "4.0"`: - set BUNDLER_VERSION=4.0.6 at the job level so every bundle invocation resolves to that version - gem install bundler -v 4.0.6 so the version is actually present (the ruby-builder tarball ships only one Bundler, and current 4.0.x tarballs no longer ship 4.0.6) Drop both once Bundler ships a fix for ruby/rubygems#9536.
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
The
RuboCopworkflow started failing on master at 2026-05-12T01:01 UTC (run 25706708602). With Ruby 4.0.4 (Bundler 4.0.11 bundled),BUNDLE_ONLY=rubocop bundle installfails to resolve this Gemfile against the multi-gemspec git sourcerails/railswhose top-level gem is in a filtered-out group, aborting with:Bundler 4.0.5 and 4.0.6 succeed; 4.0.7 through 4.0.11 fail. The upstream Bundler regression is tracked in ruby/rubygems#9536.
Pin Bundler explicitly so the workflow keeps rolling on
ruby-version: "4.0":BUNDLER_VERSION=4.0.6at the job level so everybundleinvocation in the workflow resolves to that versiongem install bundler -v 4.0.6so the version is actually present in the Ruby image (the ruby-builder tarball ships only one Bundler; current 4.0.x tarballs no longer ship 4.0.6)Once Bundler ships a fix for ruby/rubygems#9536, drop `BUNDLER_VERSION` and the install step.
Mirrors rsim/oracle-enhanced#2767.
Test plan