chore(SEC-104): bump Node to 22.23.5 / 24.22.3 / 26.13.1 (Nov 2026 security release)

Merged
GL
8d ago
+33-55

Bumps the pinned Node version to the November 2026 Node.js security release: 22.23.5 / 24.22.3 / 26.13.1. The release fixes 16 CVEs, 7 rated High (HTTP/2 use-after-free and leaks, HTTPS use-after-free via llhttp, TLS 1.2 renegotiation servername bypass of client-cert auth, https.Agent cross-policy session reuse).

Version strings only, same release line, no code change.

FileChange
package.json22.23.4 → 22.23.5
Full diff lines
    -      "version": "22.23.4",
    +      "version": "22.23.5",

Verification: CI on this PR runs on the new Node (the workflows read the pinned version). No runtime demo: a patch bump inside the same release line with no code change.

Post-merge validation: next deploy/CI run on the default branch reports the new node --version; no new error signatures in the following deploy window.

Requested by guillaume@stackone.com in Slack (#C05LDDNTJKV thread 1793813777.685889).

šŸ¤– Generated with Claude Code


Summary by cubic

Bumps the pinned Node.js runtime to 22.23.5 (November 2026 security release), fixing 16 CVEs, 7 rated High (HTTP/2 use-after-free and leaks, HTTPS use-after-free via llhttp, TLS 1.2 renegotiation servername bypass, https.Agent cross-policy session reuse).

  • Updates the devEngines.runtime pin in package.json and the matching node runtime entry (version and integrity hashes) in pnpm-lock.yaml, which pnpm requires for --frozen-lockfile installs.
  • Drops the unofficial-builds musl tarball variants for arm64 and x64 from the lockfile; the nodejs.org musl x64 variant remains.
  • No code changes. CI on this PR runs the new Node, and the next default-branch deploy should confirm node --version reports 22.23.5.