Repository navigation
chore: upgrade Node.js to 24.22.3 for November 2026 security release - #264
Conversation
Bump the CI/deploy Node pin from 24.12.0 to 24.22.3, which includes the October 2026 (24.22.1) and November 2026 (24.22.3) security fixes for HTTP/2, HTTPS, TLS, zlib and dns. Add .nvmrc so local dev matches CI. Refs #258 Co-Authored-By: Claude Opus 5.5 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
*Lighthouse ran on https://mobilitydatabase-5gwmur6ta-mobility-data.vercel.app/ * (Desktop)
*Lighthouse ran on https://mobilitydatabase-5gwmur6ta-mobility-data.vercel.app/feeds * (Desktop)
*Lighthouse ran on https://mobilitydatabase-5gwmur6ta-mobility-data.vercel.app/feeds/gtfs/mdb-2126 * (Desktop)
*Lighthouse ran on https://mobilitydatabase-5gwmur6ta-mobility-data.vercel.app/feeds/gtfs_rt/mdb-2585 * (Desktop)
*Lighthouse ran on https://mobilitydatabase-5gwmur6ta-mobility-data.vercel.app/feeds/gbfs/gbfs-flamingo_porirua * (Desktop)
|
Vercel picks the Node patch version for functions, so log process.version once per instance start to confirm the runtime in production logs. Refs #258 Co-Authored-By: Claude Opus 5.5 <[email protected]>
davidgamez
left a comment
There was a problem hiding this comment.
LGTM!
Only one minor feedback
| if (process.env.NEXT_RUNTIME === 'nodejs') { | ||
| // Log the runtime Node version once per instance start. Vercel picks the | ||
| // patch version itself, so this is how we confirm it in production logs. | ||
| console.info(`Node.js runtime ${process.version}`); |
There was a problem hiding this comment.
[suggestion]: The instrumentation.ts log isn't needed for the upgrade. Sentry already reports the Node version in the Runtime context of every server event, and this would log on every cold start. Could we drop it and check Sentry after the release instead?
Summary
Bumps the Node.js version used by CI and deploy workflows from
24.12.0to24.22.3, the patched 24.x release from the November 2026 Node.js security release (published 2026-11-10). 24.22.3 also includes the October 2026 fixes (24.22.1) originally tracked in #258..github/workflows/preview-pr.yml:NODE_VERSION24.12.0 -> 24.22.3.github/workflows/vercel-prod-on-release.yml:NODE_VERSION24.12.0 -> 24.22.3 (this also rotates the Next build cache key, which embeds the Node version).nvmrc(24.22.3) sonvm usegives local dev the same version as CIsrc/instrumentation.tslogsNode.js runtime <process.version>once per server instance start, so the production runtime version can be confirmed in Vercel logspackage.jsonengines.nodestays24.x: Vercel only reads the major version from it and picks the patch itself.Why
The November release fixes 16 flaws (7 high) in HTTP/2, HTTPS and TLS, including HTTP/2 server crashes and memory leaks, an HTTPS memory disclosure that can expose TLS private keys, and TLS SNI and renegotiation issues. Next.js serves over plain
node:httpbehind Vercel's edge, so direct exposure is low, but we were two security releases behind.Advisory: https://nodejs.org/en/blog/vulnerability/november-2026-security-releases
Verification (local, Node v24.22.3)
yarn lint: 0 errors (3 existing warnings, none in files this PR touches)yarn test:ci: 45/45 suites, 602/602 tests passednpx tsc --noEmit: cleanyarn build:prod: succeededNot covered by this PR
Node.js runtime(or check Sentry's Runtime context). We cannot pin this from the repo.nvm install && nvm usein the repo root.Refs #258
🤖 Generated with Claude Code