Skip to content

chore(deps): bump Node to 24.22.2 across every image and .nvmrc #1061

Open

Description

@chappie-daemon

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 stream fix keeping the async context of parked writes. No CVE, no API change.
  • node:24.22.2-alpine index digest sha256:8a32c8cf649a49915a66e81e7a609223c708d0adabf288ee3f4077d765542f85 (resolved from the registry; the amd64 manifest's config carries NODE_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:3 and Dockerfile:17
  • Dockerfile.railwayapp:4 and Dockerfile.railwayapp:33
  • Dockerfile.test:3
  • docker-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

  • .nvmrc reads v24.22.2; all seven image references carry the digest above and nothing else.
  • test/unit/ci/node-base-pin.spec.ts passes.
  • docker build of Dockerfile and Dockerfile.test succeeds, and the nostream-migrate container starts and runs migrations on the new base.
  • CI green on 24.22.2, including the integration stack that boots test/integration/docker-compose.yml.

Notes

  • Apply to rewrite/main first if that is where releases come from; main carries the same pins and the same test, so it is the same edit.
  • pnpm-lock.yaml records per-package engines ranges, not a toolchain pin; nothing there changes.

Activity

  1. AgrimTawani commented on Nov 11, 2026

    @AgrimTawani

    Hi @chappie-daemon! Could I be assigned to this?
    I have understood the issue, and here is my approach:

    • The issue already lists every pin — I'll follow it as-is
    • One commit: .nvmrc + all 7 image refs to node:24.22.2-alpine@sha256:8a32c8…, verifying the digest against the registry first
    • Check node-base-pin.spec.ts, docker build of Dockerfile/Dockerfile.test, and the migrate container
    • Target rewrite/main first, per the note
  2. cameri commented on Nov 15, 2026

    @cameri
    Owner

    @AgrimTawani Thank you for your interest in Nostream. Issue assigned to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

dependenciesPull requests that update a dependency file

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions