chore(runtime): raise Node floor to 22 (20 is EOL) - #65
Open
keithfawcett wants to merge 1 commit into
Open
Conversation
Node 20 reached end-of-life in March 2026 and no longer gets security patches. Bump the runtime floor to Node 22 (current LTS) across every pin: Docker build args (api/portal/router), .nvmrc, root engines (>=22), and the CI + npm-publish workflow node-version. No dependency or lockfile change; no source change. Surfaced by Codex during the SSRF hardening review. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Why
Node 20 hit end-of-life in March 2026 — no more security patches. Codex flagged it during the SSRF hardening review. This raises the floor to Node 22 (current LTS).
Changes (pins only — no source, no deps)
apps/{api,portal,router}/Dockerfile—ARG NODE_VERSION=20-alpine→22-alpine.nvmrc—20.10.0→22.20.0package.json—engines.node>=20.10.0→>=22.github/workflows/ci.yml+npm-publish.yml—node-version: '20'→'22'No
pnpm-lock.yamlchange (no dependency change), so--frozen-lockfilestays valid. CI on this PR is the real validation of the image builds + test run on 22.Notes
undici@6so it runs on both 20 and 22 — these two can merge in either order.CLAUDE.mdstill says "Node 20+" in the tech-stack blurb; left untouched here only to avoid entangling the local GitNexus auto-block in this diff — worth a one-line follow-up..nvmrc/engines on next deploy.🤖 Generated with Claude Code