Skip to content

chore(SEC-104): restore the linux-arm64-musl node runtime in the lockfile - #277

Closed
glebedel wants to merge 1 commit into
mainfrom
s2d2/sec-104-arm64-musl-runtime
Closed

glebedel wants to merge 1 commit into
mainfrom
s2d2/sec-104-arm64-musl-runtime

Conversation

@glebedel

@glebedel glebedel commented Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

When the Node 22.23.5 security bump was locked, unofficial-builds.nodejs.org had not yet published the linux-arm64-musl build, so pnpm dropped that runtime variant from pnpm-lock.yaml. It is published now. This PR adds that one variant back so pnpm install --frozen-lockfile on arm64 Alpine (for example Graviton containers) gets Node from the lockfile again.

Change

Before After
node@runtime:22.23.5 variants no linux-arm64-musl linux-arm64-musl added
Lines changed +11, -0, pnpm-lock.yaml only

The integrity sha256-UccuOhOFsQ1MhipAyEX8e+pbGeMMfhCdvcwgd8VeObs= matches node-v22.23.5-linux-arm64-musl.tar.gz in the published SHASUMS256.txt. Only the runtime block was re-resolved; no other lockfile entry moved.

Gates (head b56353c1)

Gate Result
Frozen install pnpm install --frozen-lockfile --lockfile-only resolves on the new lockfile
Hash check integrity matches the published SHASUMS256
Diff review manual: 11 added lines, one runtime variant, same in all 11 repos getting this fix
/forge:forge not run: no authored code, generated lockfile entry only
Codex security pass not run: Codex lane returns 401 in this sandbox
Demo no runtime change for existing platforms; the evidence is the frozen install above
CI see checks on this PR

Post-merge validation

Nothing to replay: x64 and glibc installs use the same entries as before. The signal is the next arm64 Alpine build or install of this repo resolving Node from the lockfile without a fallback.

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

🤖 Generated with Claude Code


Summary by cubic

Restores the linux-arm64-musl variant of the Node 22.23.5 runtime in pnpm-lock.yaml, which pnpm dropped when the SEC-104 security bump was locked because unofficial-builds.nodejs.org had not yet published that build. The build is now available, so pnpm install --frozen-lockfile on arm64 Alpine (for example Graviton containers) resolves Node from the lockfile again instead of falling back. Only the runtime entry is re-resolved; no other lockfile entries changed.

Written for commit b56353c. Summary will update on new commits.

View guided diff Turn on auto-fix

…file

pnpm records devEngines.runtime in pnpm-lock.yaml. When Node 22.23.5 was locked,
unofficial-builds.nodejs.org had not yet published linux-arm64-musl, so that variant
was dropped. It is published now; this re-resolves the runtime entries only.

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

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@glebedel glebedel self-assigned this Nov 12, 2026
@glebedel

Copy link
Copy Markdown
Contributor Author

Closing per guillaume@stackone.com's decision in Slack: we won't pull the Linux arm64 musl Node runtime from unofficial-builds.nodejs.org, because its SHASUMS are not signed by the Node release team. Without this entry, a pnpm install with a frozen lockfile on Alpine arm64 fails loudly instead of fetching an unsigned build. Nothing we build or run uses that platform: CI runs on x64 glibc, and the Docker images use glibc bases.

Automated by s2d2 for guillaume@stackone.com.

@glebedel glebedel closed this Nov 13, 2026
@glebedel
glebedel deleted the s2d2/sec-104-arm64-musl-runtime branch November 13, 2026 12:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants