Skip to content

chore: upgrade Node.js to 26.x LTS and remove runtime version log #265

Open

Description

@Alessandro100

Summary

Move the app from Node.js 24.x to Node.js 26.x, which became the active LTS line ("Lithium") with 26.13.0 on 2026-10-28. The current patched release is 26.13.1 (2026-11-10, November 2026 security release). Vercel supports 26.x and uses it as the default for new projects.

As part of this, remove the temporary runtime-version log added to src/instrumentation.ts in #264, once the production runtime version has been confirmed.

Follows on from #258 / #264 (upgrade to 24.22.3).

Current state

  • package.json engines.node: "24.x" (this is what Vercel uses to pick the major for preview builds and the function runtime)
  • .github/workflows/preview-pr.yml and .github/workflows/vercel-prod-on-release.yml: NODE_VERSION: '24.22.3'
  • .nvmrc: 24.22.3
  • @types/node: ^24.0.0
  • src/instrumentation.ts logs Node.js runtime ${process.version} (console.info) on every Node server instance start
  • Next.js 16.1.1 supports node >=20.9.0, so Next itself is not a blocker

Tasks

Node 26 upgrade

  • package.json: engines.node -> "26.x"
  • Workflows: update NODE_VERSION in preview-pr.yml and vercel-prod-on-release.yml (either an exact 26.x.y pin, or 26.x with check-latest: true so CI follows Vercel's latest patch)
  • .nvmrc -> 26
  • @types/node -> ^26, then fix any type errors (npx tsc --noEmit, yarn build:prod)
  • Check dev tooling runs on 26: Cypress, Firebase emulator (firebase-tools), Jest
  • Review Vercel's Node 26 notes on fetch behavior and the HTTP/1.1 opt-out (Advanced Node.js Usage docs) against our server-side fetches (Mobility Feed API, Google auth, Google Sheets)
  • yarn lint, yarn test:ci, yarn build:prod and e2e pass on 26
  • Ask the team to switch local Node to 26 (nvm install && nvm use)

Remove the runtime-version log

  • After deploying 26, confirm the production runtime version (Vercel runtime logs: search Node.js runtime, or Sentry: runtime.name:node, Contexts -> Runtime)
  • Remove the console.info line (and its comment) from src/instrumentation.ts. Sentry's runtime context remains the way to check the version afterwards.

Acceptance criteria

  • CI and production deploys build on Node 26.x and pass
  • Production functions confirmed running Node 26.x (>= 26.13.1)
  • src/instrumentation.ts no longer logs the Node version

Activity

  1. added
    dependenciesPull requests that update a dependency file
    tech-debtShortcuts, workarounds, or code that needs refactoring or cleanup
    on Nov 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    dependenciesPull requests that update a dependency filetech-debtShortcuts, workarounds, or code that needs refactoring or cleanup

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions