Fix ruby-head CI bundler version conflict#66
Merged
Conversation
…k pin ruby-head nightlies now ship bundler 4.1.0.dev as a default gem, but setup-ruby's default bundler resolution forces the repo's pinned BUNDLED WITH 4.0.13 onto every matrix leg, corrupting the head install (Bundler::CorruptBundlerInstallError). Override bundler: default for the head leg so it uses its own bundled version.
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
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
test (head)in CI fails withBundler::CorruptBundlerInstallErrorbecause the repo'sGemfile.lockpinsBUNDLED WITH 4.0.13, but ruby-head nightlies now ship a newer bundler (4.1.0.dev) as a default gem — setup-ruby forces the pin onto every leg including head, corrupting the install.ciaggregator check, which fails whenevertest (head)fails.bundler: defaultfor theheadmatrix leg only, so it uses ruby-head's own built-in bundler instead of the repo's pin. Other Ruby versions keep using theGemfile.lockpin as before.