chore: pin CI actions to Node-24 majors (checkout v7, setup-uv v8) via SHA#5
Merged
Conversation
Resolves the Node 20 deprecation warning by bumping the two flagged actions off their @v4 (Node 20) pins across all three workflows: - actions/checkout -> v7.0.0 (9c091bb) - astral-sh/setup-uv -> v8.2.0 (fac544c) Pinned to full commit SHAs (with version comments) rather than floating major tags for supply-chain hardening — setup-uv v8 no longer publishes @v8/@v8.0 tags for this reason, and publish.yml holds id-token: write for PyPI trusted publishing. Verified no breaking changes affect our input-less usage: setup-uv's venv-activation/manifest changes are gated behind unused inputs, and checkout's v7 fork-PR guard only applies to pull_request_target/workflow_run, which we don't use. fetch-depth: 0 (needed by hatch-vcs) is unchanged. 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.
Resolves the Node 20 deprecation warning surfaced during the v0.1.13 release run.
What changed
Bumped the two flagged actions off their
@v4(Node 20) pins across all three workflows(
ci.yml,build.yml,publish.yml):actions/checkout@v4@9c091bb(v7.0.0)astral-sh/setup-uv@v4@fac544c(v8.2.0)Why SHA-pinned
Pinned to full commit SHAs (with
# vX.Y.Zcomments) rather than floating major tags forsupply-chain hardening.
setup-uvv8 deliberately stopped publishing@v8/@v8.0tags(citing the tj-actions attack), and
publish.ymlholdsid-token: writefor PyPI trustedpublishing — the prime target to harden.
Breaking-change review (none affect us)
manifest-fileformat (v8) changes aregated behind inputs we don't pass; we invoke it with no inputs.
pull_request_target/workflow_run(neither trigger used here).
fetch-depth: 0(needed by hatch-vcs) is unchanged.Verification
CI green on this branch (run 28282338236) — checkout + setup-uv ran on Node 24, no deprecation
annotation.
build.yml(tag push) andpublish.yml(release) can't run from a branch push;they were reviewed by changelog since they share the same two action pins.
🤖 Generated with Claude Code