Repository navigation
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 1 minute. View limit details
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
viceice
force-pushed
the
viceice/feat/resolver-special-rules
branch
from
October 29, 2026 12:31
e0be158 to
baa9ce9
Compare
viceice
marked this pull request as ready for review
October 29, 2026 12:37
viceice
force-pushed
the
viceice/feat/resolver-special-rules
branch
from
October 29, 2026 14:17
baa9ce9 to
9712f12
Compare
Co-Authored-By: Claude Opus 5.5 <michael.kriese+claude-code@mend.io>
viceice
force-pushed
the
viceice/feat/resolver-special-rules
branch
from
October 29, 2026 15:14
9712f12 to
35e60c9
Compare
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.
Changes
When the image embeds data for the tool, a missing version,
latestor a partial version resolves from the tool-versions data first:latestis the newest LTS release.latestis thelatestdist-tag; a partial version skips deprecated releases. A dist-tag which needs a newer containerbase falls back to the newest installable release.install-npm,install-gemandinstall-pipnever read the data, they keep using their registries.Otherwise the tools use their own lookup, as before:
Exact versions keep their old resolvers. git follows with #8077; poetry follows once the data marks yanked releases. Docs follow in the top layer of the stack.
Part of #7897.
Context
Please select one of the following:
AI assistance disclosure
Did you use AI tools to create any part of this pull request?
Please select one option and, if yes, briefly describe how AI was used (e.g., code, tests, docs) and which tool(s) you used.
Code and tests by Claude Code (Claude Opus 5.5), reviewed by @viceice.
Use of AI in replying to PR comments
Who answers review comments:
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via:
🤖 Generated with Claude Code