Summarize cooldown-skipped versions at the end of install, update, and lock - #9762
Merged
Merged
Conversation
…d lock When cooldown silently resolves an older version, users comparing environments with different cooldown settings can't tell why they got different versions. Collect the versions the resolver excluded, and after a successful resolution print the newest skipped version per gem once the command finishes. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
hsbt
added a commit
that referenced
this pull request
Aug 5, 2026
Without a summary, a version the cooldown kept out is indistinguishable from a version that does not exist, which reads as environments resolving different versions for no visible reason. Match the Bundler summary added in #9762: after a completed install or update, report per gem the newest skipped version, when it will become available, and the version resolved instead. The resolver accumulates skipped candidates and reports only those newer than the resolved version and satisfying the final requirements. gem update also reports skipped name tuples newer than the version the update settled on. gem outdated already annotates versions within the window, so it gets no summary. Co-Authored-By: Claude Fable 5 <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.
When cooldown silently resolves an older version, there is no way to tell why an environment with a different cooldown setting picked a newer one. A user reported puzzling over CI installing
rbs4.1.2 while their local machine, with a cooldown configured, kept getting the older release.This collects the versions the resolver excluded and prints the newest skipped version per gem after
bundle install,bundle update, andbundle lockfinish. Only versions satisfying every requirement of the final resolution are reported, so the summary never claims a version the resolver could not have picked anyway.No message is printed when nothing was skipped or when install uses an up-to-date lockfile.