Skip to Content

All apps move to Node 22 LTS

Shipped 2026-10-19

Every deployed app ran Node 20.11.1. Node 20 reached end-of-life on 30 April 2026, so it was getting no security patches, and 20.11.1 was well behind even the last 20.x release. Dependencies had moved past it too. Every app installed packages that declare Node ≥ 20.19 (Sentry 11, ESLint 9.x, rolldown, @noble/hashes under otplib), and the pin was blocking Dependabot bumps.

Rollout

PhaseAppsPR
1admin, assistant (internal)#980
2www#982
—api JSON imports fixed for Node 22#983
3api (with db-migrate and iba-dev-api)#984

Each phase waited for the previous one to deploy cleanly. admin went first because it builds through the same DO buildpack as www and api, so it proved the buildpack would accept the new engines value before a public app depended on it.

How Node is pinned now

  • DO buildpack apps (admin, www, api) declare engines.node: "22.x". The buildpack installs the newest 22.x it knows of on each deploy (22.22.2 at rollout), so Node security patches arrive with ordinary deploys instead of waiting for someone to edit a pin. That waiting is how 20.11.1 went stale.
  • Docker images (assistant/Dockerfile, docker/*/Dockerfile) pin node:22.23.3 exactly, so a given commit always builds the same image.

The lockfiles changed only their recorded engines line. Regenerating them with npm 10.9 would also have stripped the libc markers that keep glibc native binaries out of the musl Alpine image.

What testing caught

The API’s test suite passed on Node 22, but a local boot followed by GET /api returned 500. Thirty-nine JSON imports used import assertions, which Node 22 removed. That was fixed and deployed on Node 20 first (#983, with its own changelog entry), so this PR changes the runtime and nothing else.

Last updated on