Skip to content

fix!: move to Node.js 24 for November 2026 security releases - #222

Open
fredericsimard wants to merge 2 commits into
masterfrom
ci/node-24/2026-11-12
Open

fredericsimard wants to merge 2 commits into
masterfrom
ci/node-24/2026-11-12

Conversation

@fredericsimard

@fredericsimard fredericsimard commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

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

  • .nvmrc 18 to 24.22.3 (Netlify build and Functions runtime)
  • engines node >=18.0.0 to >=24.22.3
  • CI Node 18/20 to 24.22.3, pinned exactly: with node-version: 24, actions/setup-node used the runner's cached 24.22.2, which yarn rejects against the new engines minimum
  • 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.

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

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>
@netlify

netlify Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

✅ Deploy Preview for gbfs-validator ready!

Name Link
🔨 Latest commit 2dd30ee
🔍 Latest deploy log https://app.netlify.com/projects/gbfs-validator/deploys/6af628386ee5fc82e17f015c
😎 Deploy Preview https://deploy-preview-222--gbfs-validator.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
🤖 Make changes Run an agent on this branch

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>
Comment thread .github/workflows/publish_validator.yml Resolved
uses: actions/setup-node@v7.0.0
with:
node-version: '20'
node-version: '24.22.3'

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We want >24.22.3, all 24.x versions before that are vulnerable.

@jcpitre jcpitre Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok perfect then.

This branch has not been deployed

No deployments
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.

2 participants