Resolve official uv self-update versions before axoupdater#18674
Merged
Conversation
4bc25a1 to
3a51035
Compare
zanieb
reviewed
Mar 23, 2026
zanieb
approved these changes
Mar 23, 2026
Member
|
We might want to continue to ban |
Member
|
Generally, the |
Member
Author
|
Alright, I'll add a check that ensures the version number roundtrips cleanly ( |
e514256 to
d884aa8
Compare
zanieb
reviewed
Mar 23, 2026
d884aa8 to
e8f3afe
Compare
konstin
pushed a commit
that referenced
this pull request
Mar 24, 2026
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.
This PR changes
uv self updateto use theuv.ndjsonhosted athttps://raw.githubusercontent.com/astral-sh/versions/main/v1/to resolve the desired uv version.This behavior change happens only if:
Important
Because of the move to pep440 version specifiers, this means that
uv self update 0.10will now resolve to0.10.0instead of failing. This is consistent withuvx uv@0.10behavior, but it isn't intuitive. We could consider failing such commands like before, but I chose consistency withuvx uv@0.10, because I'm planning to add version bounds (uv self update '<0.11') too, which would make it clearer that these are Python version strings.Towards #18503.
Test Plan
Happy path:
One of the many sad paths: