Repository navigation
ci: bump checkout/setup-node to v5 + read-only token - #77
Merged
Merged
Conversation
actions/checkout@v4 and actions/setup-node@v4 now emit GitHub's "Node.js 20 is deprecated, forced to run on Node.js 24" runner warning. Bump both to @v5 to clear it (build target node-version: 20 is unchanged). Also add a least-privilege top-level permissions: contents: read block — the build only needs checkout, no write scopes. 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
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.
Follow-up to #76 (the CI build workflow).
What
actions/checkout@v4→@v5andactions/setup-node@v4→@v5.permissions: contents: readblock.Why
The
@v4actions now emit GitHub's runner warning "Node.js 20 is deprecated… forced to run on Node.js 24". Bumping to@v5clears it. This is the action runtime only — the build target (node-version: 20) is unchanged.The build only needs
checkout, so a read-only token is sufficient; scopingpermissionsdown is best-practice hardening.Risk
Minimal — no behavior change to the build itself; CI re-running on this PR confirms it stays green.
🤖 Generated with Claude Code