Repository navigation
Conversation
…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>
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the Node 22.23.5 security bump was locked, unofficial-builds.nodejs.org had not yet published the
linux-arm64-muslbuild, so pnpm dropped that runtime variant frompnpm-lock.yaml. It is published now. This PR adds that one variant back sopnpm install --frozen-lockfileon arm64 Alpine (for example Graviton containers) gets Node from the lockfile again.Change
node@runtime:22.23.5variantspnpm-lock.yamlonlyThe integrity
sha256-UccuOhOFsQ1MhipAyEX8e+pbGeMMfhCdvcwgd8VeObs=matchesnode-v22.23.5-linux-arm64-musl.tar.gzin the published SHASUMS256.txt. Only the runtime block was re-resolved; no other lockfile entry moved.Gates (head
b56353c1)pnpm install --frozen-lockfile --lockfile-onlyresolves on the new lockfilePost-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-muslvariant of the Node 22.23.5 runtime inpnpm-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, sopnpm install --frozen-lockfileon 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.