Repository navigation
ci: pin highest eligible gem version in global pinner - #544
Merged
Merged
Conversation
Signed-off-by: Arjun Rajappa <arjun.rajappa@ibm.com>
Signed-off-by: Arjun Rajappa <arjun.rajappa@ibm.com>
arjun-rajappa
force-pushed
the
ci/global-pinner-highest-version
branch
from
November 4, 2026 06:34
6c670fa to
40771e9
Compare
Signed-off-by: Arjun Rajappa <arjun.rajappa@ibm.com>
…parsing Signed-off-by: Arjun Rajappa <arjun.rajappa@ibm.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
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.
The date pinner chose the most recently published eligible version. When
rackreleased 3.2.8, 3.1.23 and 2.2.25 within minutes of each other, it pinnedrackto 2.2.25. That conflicts withrackup2.3.1, which needsrack >= 3, sobundle installfailed.