fix(docker): use Node 22.14 + corepack via packageManager field - #2
Merged
Conversation
The v0.3.0 release pipeline failed at `corepack prepare pnpm@latest --activate`
inside the Docker frontend build stage with:
Internal Error: Cannot find matching keyid: ...
at verifySignature (corepack.cjs:21535:47)
Reproduced locally with `docker run --rm node:22.12.0-slim sh -c
'corepack enable && corepack prepare pnpm@latest --activate'`. Node 22.12.0
ships corepack 0.30, whose baked-in key set predates the keys used to sign
current pnpm releases — `pnpm@latest` resolves to a pnpm version that
corepack 0.30 refuses to install.
Two fixes:
1. Bump to node:22.14.0-slim (corepack 0.31+ has the current key set).
2. Drop `corepack prepare pnpm@latest`. `pnpm install` triggers corepack to
read the `packageManager` field from package.json (pnpm@9.15.1 + integrity
hash) and download exactly that version — same pnpm as local dev, no
floating tag, no future signature-key drift.
Verified locally: `docker run … node:22.14.0-slim sh -c 'corepack enable &&
pnpm install --frozen-lockfile'` now succeeds and uses pnpm 9.15.1 from the
lockfile.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Picks up active LTS instead of maintenance LTS: - node:24-slim ships corepack 0.34 (current key set, no signature bug) - Node 24 is the active LTS line until Oct 2026; 22 is in maintenance - Stays off Node 25+ which unbundled corepack — keeping the clean `corepack enable` install path Verified end-to-end: `docker run --rm -v \$PWD/web:/app/web -w /app/web node:24-slim sh -c 'corepack enable && pnpm install --frozen-lockfile && pnpm build'` builds the static SPA cleanly with pnpm 9.15.1 from the packageManager field. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.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
1 participant
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.
Summary
The v0.3.0 release pipeline failed at the Docker frontend build stage with:
```
Internal Error: Cannot find matching keyid: ...
at verifySignature (corepack.cjs:21535:47)
```
Reproduced locally — `node:22.12.0-slim` ships corepack 0.30 with an old signing-key set that doesn't recognize current pnpm signatures, so `corepack prepare pnpm@latest --activate` exits 1.
What changed
Test plan
🤖 Generated with Claude Code