ci: Fix setup-uv pin (v8 → v7) to unbreak main#14
Open
beneboy wants to merge 1 commit into
Open
Conversation
Node 20 actions are forced off on 2026-06-16 and removed 2026-09-16.
Bump to the current Node 24 moving major tags across CI and release
workflows:
- actions/checkout v4 -> v6
- astral-sh/setup-uv v5 -> v7 (v7 is the highest moving major
tag and already runs on Node 24;
no floating v8 tag exists yet)
- actions/upload-artifact v4 -> v7
- actions/download-artifact v4 -> v8
Inputs in use (enable-cache, name, path, retention-days) are unchanged
across these majors. pypa/gh-action-pypi-publish stays on its maintained
release/v1 floating tag (already on a supported Node). Each runtime
verified via runs.using in the action.yml at the pinned tag.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
beneboy
force-pushed
the
ci/fix-setup-uv-v7
branch
from
f03e907 to
3d8c360
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
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.
Context
The GitHub Actions release/CI workflows were emitting Node 20 deprecation warnings (Node 20 is forced off 2026-06-16). The bump commit
be928b5(landed onmain) updated four actions to their latest Node 24 majors — but pinnedastral-sh/setup-uv@v8, which does not exist as a moving tag: the project shipsv8.xreleases but the highest bare major tag isv7. CI onmainwent red withUnable to resolve action astral-sh/setup-uv@v8.Fix
Pin
setup-uvto@v7, which already runs on Node 24 (v6 is still Node 20), so the deprecation goal is still met.actions/checkout@v6astral-sh/setup-uv@v7(was@v8❌)actions/upload-artifact@v7actions/download-artifact@v8pypa/gh-action-pypi-publishstays on its maintained@release/v1floating tag (already on a supported Node).Each runtime confirmed via
runs.usingin the action'saction.ymlat the pinned tag.Validation
CI on this PR exercises
checkout,setup-uv, andupload-artifact. Thedownload-artifact@v8path only runs on tag/workflow_dispatch(release workflows), so it isn't covered here — but thev8moving tag exists and is node24.🤖 Generated with Claude Code