Files
lefarcenandClaude Opus 4.7 d5549bf016 fix(tools-pack): replace corepack with npx in linux container build
release-stable run 25386360556 failed at the build_linux job with:
  bash: line 1: corepack: command not found
  Error: docker build exited with code 127

Although Node 16.10+ ships corepack, the `electronuserland/builder:base`
image strips the corepack binary, so the inner `bash -lc` we pass to
`docker exec` blows up before pnpm install ever starts. We can't
`corepack enable` ourselves either — the container runs as the host's
non-root uid (--user) and corepack would try to write shims next to the
root-owned system Node binary.

Switch to `npx --yes pnpm@10.33.2`:
- npx ships with npm and is always present in the image
- --yes skips the install confirmation
- package caches under $HOME/.npm/_npx (writable by the unprivileged user)
- the pinned version matches the `packageManager` field in the root
  package.json, preserving reproducibility

Both invocations switch in lockstep:
- `corepack pnpm install --frozen-lockfile` → `npx --yes pnpm@10.33.2 install --frozen-lockfile`
- `corepack pnpm tools-pack linux build ...` → `npx --yes pnpm@10.33.2 tools-pack linux build ...`

Local verify: pnpm --filter @open-design/tools-pack run typecheck (exit 0).
Full e2e verification needs the actual docker run on a Linux runner —
the next release-stable dispatch will exercise it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-06 00:00:08 +08:00
..
2026-05-05 23:39:40 +08:00