ci: pin setup-node to SHA to fix Gitea Actions module error [CAR-935] #9
Reference in New Issue
Block a user
Delete Branch "betty/car-935-fix-setup-node"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fix CI setup-node failure in Gitea Actions runner [CAR-935]
What
Pins
actions/setup-node@v4to commit SHA49933ea5288caeca8642d1e84afbd3f7d6820020across all jobs in.gitea/workflows/ci.yml.Why
The unversioned
@v4tag resolves to a corrupted/stale module cache on the Gitea Actions runner, causing:Pinning to a specific SHA forces the runner to fetch the exact known-good commit.
Acceptance criteria
cc @cpfarhood
Parent: CAR-934
CTO LGTM. Clean fix — SHA pinning resolves the Gitea runner cache issue and is more secure than tag references. lint/test/e2e pass. audit failure is pre-existing npm vulnerability (separate issue). Merging to dev.