Repository navigation
ci: always resolve latest Node 22 patch in setup-node - #208
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
Node's 2026-10-21 security release fixes 10 CVEs, including CVE-2026-111497, an out-of-bounds write in the bundled Brotli decoder that
fetchreaches whenever it decompresses abrresponse. The fixed versions are 22.23.4, 24.22.1 and 26.12.1. Withoutcheck-latest, setup-node reuses whatever 22.x is already cached on the runner, which can be older than the fix, so this makes CI always resolve the newest 22.x patch.The Dockerfile (
node:22-slim, which Docker Hub rebuilt with 22.23.4 on 10-21) and Vercel (24.x, patched by Vercel) need no repo change, only a rebuild with--pulland a redeploy.Verification: check that the Setup Node step in this PR's CI log resolves 22.23.4 or later.