{{ message }}
Bump setup-uv to v10.0.1 to tolerate transient manifest fetch failures - #618
Merged
Merged
Conversation
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.
PR #612's
pr-core-pythonjob failed in the setup-uv step with##[error]fetch failedwhile retrieving the uv version manifest from raw.githubusercontent.com, before any repository code ran. The pinned v7 action treats one failed manifest fetch as fatal.Upstream fixed this failure class in v10.0.1 ("Tolerate transient manifest timeouts", astral-sh/setup-uv#1016). This bumps all 18 pinned usages across 10 workflow files from the v7 SHA to the v10.0.1 SHA.
Breaking changes between v7 and v10, checked against our usage:
manifest-fileformat; we useversion-file(.github/uv.toml), unaffected.prune-cachedefault to false; we never set it, and the new default matches upstream's PyPI-load reasoning.enable-cache: autoforpull_request_target,workflow_run, andreleaseevents as cache-poisoning protection. Our PR/test workflows setenable-cache: trueexplicitly; the only usage affected is one step in python-release.yml, which loses caching on release events. That is accepted as intended hardening rather than overridden.Verified: zero v7 pins remain; every usage was audited for its cache setting and trigger events.