fix(ci): pin actions/setup-node version comment to v6.3.0#792
Conversation
The SHA pinned for actions/setup-node resolves to tag v6.3.0, but the comment said `# v6`. zizmor's ref-version-mismatch audit flags this and fails the security workflow. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
@claude review |
27976d5 to
9943897
Compare
There was a problem hiding this comment.
LGTM — purely a comment fix aligning the version label with the pinned SHA, no behavioral change.
Extended reasoning...
Overview
Updates 4 inline comments from # v6 to # v6.3.0 across ci.yml and release.yml. The action SHA (53b83947a5a98c8d113130e565377fae1a50d02f) is identical in all four locations before and after — only the human-readable comment changes.
Security risks
None. The pinned SHA is unchanged, so the exact same action binary executes. The fix actually improves the security posture by making the zizmor ref-version-mismatch check pass, which enforces that comments accurately reflect the resolved tag.
Level of scrutiny
Minimal scrutiny required. This is a pure comment correction with zero runtime impact. The change is mechanical, consistent across all four call sites, and clearly motivated by the CI security linter failure.
Other factors
No bugs were reported. No outstanding reviewer comments. The diff is small, self-contained, and follows the existing pattern of pinning actions by SHA with a version comment.
Summary
actions/setup-noderesolves to tagv6.3.0, but the comment said# v6, which zizmor flags asref-version-mismatchand fails the security workflow.ci.yml, 1 inrelease.yml) to# v6.3.0.Test plan
actions/setup-nodeas before (no behavior change — same SHA)🤖 Generated with Claude Code
Disclaimer: Experimental PR review
Greptile Summary
This PR corrects the version comment on all four
actions/setup-nodeusages from# v6to# v6.3.0to match the pinned SHA53b83947a5a98c8d113130e565377fae1a50d02f, resolving aref-version-mismatchfinding from zizmor. No behavior changes — the SHA and workflow logic are identical.Confidence Score: 5/5
Safe to merge — comment-only change with no behavior impact.
All four changes are purely cosmetic comment corrections that align the version tag with the pinned SHA. No logic, no dependencies, no security surface altered.
No files require special attention.
Important Files Changed
actions/setup-nodeversion comments from# v6to# v6.3.0; SHA and workflow logic unchanged.actions/setup-nodeversion comment from# v6to# v6.3.0; SHA and workflow logic unchanged.Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A["zizmor lint check"] -->|"ref-version-mismatch: SHA ≠ comment tag"| B["Security workflow fails"] B --> C["PR fix: comment updated\n# v6 → # v6.3.0\n(SHA unchanged)"] C --> D["zizmor lint passes"] D --> E["CI & release workflows\nrun as before"]Reviews (1): Last reviewed commit: "fix(ci): pin actions/setup-node version ..." | Re-trigger Greptile