chore(template): SHA-pin and bump astral-sh/setup-uv to v8.1.0#14
Open
xaviedoanhduy wants to merge 2 commits into
Open
chore(template): SHA-pin and bump astral-sh/setup-uv to v8.1.0#14xaviedoanhduy wants to merge 2 commits into
xaviedoanhduy wants to merge 2 commits into
Conversation
Pin setup-uv@v6 → SHA of v6.8.0 in the scaffolded action template. Floating major tags are mutable; SHA pins are immutable. Note: upgrade v6→v8 in the template is a separate task.
3 tasks
Contributor
did you spot any? it just installs uv so I wonder what could change that much |
After review on #14, no functional breaking change for the install-uv path between v6 → v8 (inputs `version`, `enable-cache`, `cache-suffix` unchanged). The v8.0.0 floating-tag removal is moot since we pin to commit SHA. Aligns the scaffolded action with the repo's own CI workflow (.github/workflows/pre-commit.yaml), which already uses v8.1.0. Benefits picked up along the way: - v7.5+: uv release metadata served from Astral mirror, avoiding GitHub API rate limits during version resolution. - v8.0.0: immutable releases.
xaviedoanhduy
changed the title
Member
Author
|
fair point — I checked the v7+v8 release notes and didn't spot any breaking change that affects the template's install-uv path. The inputs we use ( the relevant breaking changes:
i bumped the template to |
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
2 participants
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.
Why
Follow-up to #13.
The scaffolded
setup-python-env/action.yamlusedastral-sh/setup-uv@v6(mutable floating tag). This pins it to a commit SHA and bumps to v8.1.0,
matching the repo's own CI workflow (already on v8.1.0 since #13).
What
astral-sh/setup-uv@v6→@08807647e7069bb48b6ef5acd8ec9567f424441b # v8.1.0actions/setup-python@v6kept on version tag (GitHub-owned, same pragmaticstance as #13).
v6 → v8: breaking changes reviewed
The action only installs uv. Inputs used by the template (
version,enable-cache,cache-suffix) are unchanged across v6/v7/v8.removed
server-urlinput (template doesn't use it).@vX.Y.Zor SHA.Moot here since we pin to SHA. Also removed deprecated
manifest-filelegacy format (template doesn't use it).
Picked up along the way:
rate limits during version resolution.
Test plan
pre-commit.yamlandtest.yamlworkflows run green with setup-uv v8.1.0