Skip to content

Pin Node 22.23.4 in CI (October 2026 security release) - #13

Merged
samyakLambda merged 2 commits into
mainfrom
ci/setup-node-check-latest
Oct 30, 2026
Merged

samyakLambda merged 2 commits into
mainfrom
ci/setup-node-check-latest

Conversation

@samyakLambda

@samyakLambda samyakLambda commented Oct 29, 2026 •

Copy link
Copy Markdown
Collaborator

Pins the two actions/setup-node steps to Node 22.23.4, the October 2026 Node.js security release for the 22 line.

node-version: "22" takes whatever Node 22 a runner image already caches. Runner images update roughly weekly, so after a security release a job can keep running the previous patch. An exact pin removes that drift.

Changes: test-scripts.yml and update-formula.yml move from "22" to "22.23.4". No step bodies change, so the formula anchors and the scripts that extract step bodies are unaffected.

Checked:

  • actionlint is clean.
  • All six scripts/test-*.sh pass locally.

🤖 Generated with Claude Code

samyakLambda and others added 2 commits October 29, 2026 17:51
setup-node reuses the Node a runner already caches for the requested
line, so a job can keep running an older patch after a Node security
release. check-latest resolves the newest release of the line instead.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Use the exact October 2026 security release the org advisory lists,
not whatever the newest Node 22 is when a job runs.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@samyakLambda samyakLambda changed the title Pick up patched Node in CI with setup-node check-latest Pin Node 22.23.4 in CI (October 2026 security release) Oct 29, 2026
@samyakLambda
samyakLambda merged commit e584563 into main Oct 30, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant