Repository navigation
Description
Node 24.22.2 is the latest v24 stable release. The repo builds and tests on 24.22.1 everywhere, so the base moves in six image references plus .nvmrc.
Target
- v24.22.2 — released 2026-10-28, LTS "Krypton" (release notes). Patch on the same minor line: V8 backports and one
streamfix keeping the async context of parked writes. No CVE, no API change. node:24.22.2-alpineindex digestsha256:8a32c8cf649a49915a66e81e7a609223c708d0adabf288ee3f4077d765542f85(resolved from the registry; the amd64 manifest's config carriesNODE_VERSION=24.22.2, image created 2026-10-28T20:56Z).
The npm shipped in 24.22.2 is 11.19.1; packageManager stays pnpm@10.33.0.
Current state (identical on main and rewrite/main)
Every reference below is node:24.22.1-alpine@sha256:06d7adf3e0ef61a13f1d28682726366f97a15aa1888c934d3ecec86c33918b53:
Dockerfile:3andDockerfile:17Dockerfile.railwayapp:4andDockerfile.railwayapp:33Dockerfile.test:3docker-compose.yml:129(nostream-migrate)test/integration/docker-compose.yml:71(migrations-test).nvmrc—v24.22.1
.github/workflows/* read node-version-file: .nvmrc, so the .nvmrc bump carries CI and the website deploys. dependabot-changeset.yml:39 says node-version: '24' and needs no change. package.json engines.node is >=24.14.1 — already satisfied, leave it alone or raise it deliberately, but not as a side effect.
Guard
test/unit/ci/node-base-pin.spec.ts already enforces this: every FROM node:… and image: node:… must be digest-pinned, and the set of distinct references must have length 1. A partially applied bump fails that test, which is the point — one commit changes all of them.
Acceptance
.nvmrcreadsv24.22.2; all seven image references carry the digest above and nothing else.test/unit/ci/node-base-pin.spec.tspasses.docker buildofDockerfileandDockerfile.testsucceeds, and thenostream-migratecontainer starts and runs migrations on the new base.- CI green on
24.22.2, including the integration stack that bootstest/integration/docker-compose.yml.
Notes
- Apply to
rewrite/mainfirst if that is where releases come from;maincarries the same pins and the same test, so it is the same edit. pnpm-lock.yamlrecords per-packageenginesranges, not a toolchain pin; nothing there changes.
Activity
AgrimTawani commentedon Nov 11, 2026
Hi @chappie-daemon! Could I be assigned to this?
I have understood the issue, and here is my approach:
.nvmrc+ all 7 image refs tonode:24.22.2-alpine@sha256:8a32c8…, verifying the digest against the registry firstnode-base-pin.spec.ts,docker buildofDockerfile/Dockerfile.test, and the migrate containerrewrite/mainfirst, per the notecameri commentedon Nov 15, 2026
@AgrimTawani Thank you for your interest in Nostream. Issue assigned to you.