ci: upgrade checkout/setup-node to Node 24 (v5) - #4
Conversation
Bumps actions/checkout from v3.6.0 to v5.0.1 and actions/setup-node from v3.9.1 to v5.0.0, moving off the deprecated Node.js 20 runtime. SHA pins are retained (updated to the v5 commit SHAs). Built on top of the 'CI/CD Security Improvements with Step Security' PR. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
Claude: why do these build_nodejs tests fail? fix. |
Restore the BuildKit test-skip guard that exists on master (PR #3) but was missing on this branch, which descended from a pre-PR#3 state via the fix-memory-leak merge. The external dockerode suite's BuildKit integration tests ("should follow BuildKit build progress", "should build image with buildKit") time out after 60s in CI and are known-flaky; master already excludes them on the 14/16/18/19 lanes. This makes build_nodejs green while keeping the Node 24 SHA-pinned checkout/setup-node upgrades. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Fixed the failing
|
c895e4d
into
chore/GHA-142316-stepsecurity-remediation
Summary
Moves the CI workflow off the deprecated Node.js 20 runtime by upgrading the GitHub Actions to their Node 24 (v5) releases:
actions/checkoutv3.6.0→v5.0.1actions/setup-nodev3.9.1→v5.0.0SHA pins are retained and updated to the corresponding v5 commit SHAs, preserving the pinning introduced by the open 'CI/CD Security Improvements with Step Security' PR. This PR is stacked on top of that branch (
chore/GHA-142316-stepsecurity-remediation) so the harden-runner step andpermissions:block are kept — it complements, rather than duplicates, that work.Verification
yaml.safe_load).Generated by Claude Code Service (see job).
Respond to this PR with the prefix "Claude: " to trigger an action on this PR.