ci: bump astral-sh/setup-uv to v8.1.0 (Node 24)#7
Merged
Conversation
The pinned setup-uv ran on Node 20, which GitHub Actions force-migrates to Node 24 on 2026-06-16 and removes on 2026-09-16. Bump to v8.1.0 to clear the deprecation warning before the cutoff. - release.yml: repin SHA -> 08807647e7069bb48b6ef5acd8ec9567f424441b (v8.1.0) - lint.yml: @v5 -> @v8 (keeps this file's tag-pin style) Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Why
The pinned
astral-sh/setup-uvran on Node 20, which GitHub Actions force-migrates to Node 24 on 2026-06-16 and removes on 2026-09-16. This was the lone deprecation annotation on thev2.1.0release run.What
release.yml: repin SHA →08807647e7069bb48b6ef5acd8ec9567f424441b(v8.1.0, Node 24)lint.yml:@v5→@v8(keeps this file's tag-pin convention)No behavior change;
enable-cacheand all inputs are unchanged in v8.Release impact
Typed
ci:, so semantic-release will not cut a new version on merge (per.releaserc.json). The release workflow will run on the merge commit, find nothing releasable, and the publish step no-ops viaskip-existingagainst the already-published2.1.0.🤖 Generated with Claude Code