Repository navigation
fix!: move to Node.js 24 for November 2026 security releases - #222
Open
fredericsimard wants to merge 2 commits into
Open
fredericsimard wants to merge 2 commits into
fredericsimard wants to merge 2 commits into
Conversation
Wednesday, November 11, 2026, [the Node.js project released emergency security updates](https://nodejs.org/en/blog/vulnerability/november-2026-security-releases) across all three active release lines (26.x, 24.x, and 22.x) to patch 16 vulnerabilities, including 7 high-severity flaws. `The vulnerabilities primarily affect Node.js's built-in HTTP/2, HTTPS, and TLS server implementations.` `24.22.3 is a patched version.` Changes: .nvmrc 18 to 24 (Netlify build and Functions runtime), engines node >=18.0.0 to >=24.22.3, CI Node 18/20 to 24, actions/checkout v2/v3.4.0 to v7.0.1, actions/setup-node v3/v4 to v7.0.0. Node 18 is end-of-life and not covered by the security releases. BREAKING CHANGE: Node.js 18 and 20 are no longer supported; engines now require Node.js >=24.22.3. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Deploy Preview for gbfs-validator ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
With node-version 24, actions/setup-node used the runner's cached 24.22.2, which yarn rejects against engines >=24.22.3. Pin the patched release in both workflows and in .nvmrc so CI and Netlify run 24.22.3. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jcpitre
reviewed
Nov 16, 2026
jcpitre
reviewed
Nov 16, 2026
| uses: actions/setup-node@v7.0.0 | ||
| with: | ||
| node-version: '20' | ||
| node-version: '24.22.3' |
Contributor
There was a problem hiding this comment.
Do we want the version pinned? Or do we want to avoid 24.22.2?
Suggested change
| node-version: '24.22.3' | |
| node-version: 24 | |
| check-latest: true |
Contributor
Author
There was a problem hiding this comment.
We want >24.22.3, all 24.x versions before that are vulnerable.
Contributor
There was a problem hiding this comment.
But with the way you want to change it I think you'll get exactly 24.22.3. You wont get the new releases.
We already know that the latest is at least 24.22.3. So with check-latest you should not get 24.22.2.
It's kind of a detail. It will work the way it is, so I'm approving.
Contributor
Author
There was a problem hiding this comment.
Ok perfect then.
jcpitre
approved these changes
Nov 19, 2026
This branch has not been 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.
Wednesday, November 11, 2026, the Node.js project released emergency security updates across all three active release lines (26.x, 24.x, and 22.x) to patch 16 vulnerabilities, including 7 high-severity flaws.
The vulnerabilities primarily affect Node.js's built-in HTTP/2, HTTPS, and TLS server implementations.
24.22.3 is a patched version.
Changes
.nvmrc18 to 24.22.3 (Netlify build and Functions runtime)node-version: 24, actions/setup-node used the runner's cached 24.22.2, which yarn rejects against the new engines minimumNode 18 is end-of-life and not covered by the security releases.
Testing
In node:24 (v24.22.3): yarn install --frozen-lockfile, yarn workspaces run test (33 tests, 4 suites) and yarn build pass. Workflow YAML parses. The Netlify deploy preview will confirm the Functions runtime picks up Node 24.22.3.
🤖 Generated with Claude Code