Summary
We're currently pinned to Node 22 in four places:
Node 24 ("Krypton") is Active LTS and a good target for the next bump (Node 26 isn't LTS until October 2026, so it's not the right choice yet).
A security release for the 22.x/24.x/26.x lines was announced for 2026-07-28 (see Node.js security release notice), but the patched version numbers weren't public as of this writing. Latest known-good Node 24 release is 24.18.0 (2026-06-23).
Task
Once the patched Node 24 version from the 2026-07-27 security release is published:
🤖 Written by Claude Sonnet 5 (claude-sonnet-5).
Summary
We're currently pinned to Node 22 in four places:
FROM node:22.21.1-bookworm-slim"node": "22.17.0"node-version: [22]"@types/node": "~22.20.0"Node 24 ("Krypton") is Active LTS and a good target for the next bump (Node 26 isn't LTS until October 2026, so it's not the right choice yet).
A security release for the 22.x/24.x/26.x lines was announced for 2026-07-28 (see Node.js security release notice), but the patched version numbers weren't public as of this writing. Latest known-good Node 24 release is 24.18.0 (2026-06-23).
Task
Once the patched Node 24 version from the 2026-07-27 security release is published:
FROM node:...base image (and digest pin) in the Dockerfilenodefield in package.jsonnode-versionmatrix entries in .github/workflows/frontend.yml (both jobs)@types/nodein package.json to match the new major (~24.x.x)npm run i,npm run build, and CI pass on the new version🤖 Written by Claude Sonnet 5 (claude-sonnet-5).