fix(ci): install caxa via npx to unblock binary release under pnpm v11#9367
Merged
matthewkeil merged 1 commit intoMay 13, 2026
Merged
Conversation
`pnpm add -g @chainsafe/caxa@3.0.6` fails on v1.43.0-rc.3 (run 25820616462)
with:
ERROR The configured global bin directory
"/home/runner/setup-pnpm/node_modules/.bin/bin" is not in PATH
Since ChainSafe#9299 bumped pnpm to v11 (and `pnpm/action-setup` to v5), the action
still exports `PNPM_HOME=/home/runner/setup-pnpm/node_modules/.bin` and
puts that exact dir on PATH, but pnpm v11 now resolves the global bin
directory as `$PNPM_HOME/bin` (subdir), which is not on PATH, so
`pnpm add -g` hard-fails before caxa is installed.
`publish-rc.yml` / `publish-stable.yml` are the only callers of
`binaries.yml`, so this only surfaced on the v1.43.0-rc.3 publish.
The `pnpm add -g` line was redundant anyway — the next line is `npx caxa`,
which fetches caxa on demand. Inline the version pin with
`npx -y -p @chainsafe/caxa@3.0.6 caxa ...` so we drop the global install
entirely and stop touching the pnpm global bin path.
🤖 Generated with AI assistance
Contributor
|
Note Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported. |
nflaig
approved these changes
May 13, 2026
Contributor
Author
|
@gemini-code-assist Noted — file type (CI YAML) not supported by Gemini, no action needed. Thanks for the status note. |
Contributor
|
Note Gemini is unable to generate a issue-comment-reply for this pull request due to the file types involved not being currently supported. |
matthewkeil
approved these changes
May 13, 2026
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
3 participants
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
v1.43.0-rc.3binary release (run 25820616462) fails at thepnpm add -g @chainsafe/caxa@3.0.6step in.github/workflows/binaries.ymlwith:Root cause
#9299 bumped pnpm v10 → v11 and
pnpm/action-setupv4 → v5. action-setup v5 still exportsPNPM_HOME=/home/runner/setup-pnpm/node_modules/.binand puts that exact dir onPATH, but pnpm v11'spnpm add -gnow resolves the global bin as$PNPM_HOME/bin(a subdirectory), which is not onPATH, so it aborts before caxa is ever installed.publish-rc.yml/publish-stable.ymlare the only callers ofbinaries.yml, which is why this only surfaced now on the v1.43.0-rc.3 publish —unstableCI doesn't exercise this path.Fix
The
pnpm add -gline was redundant — the very next line isnpx caxa ..., which already fetches caxa on demand. Drop the global install and inline the version pin withnpx -y -p @chainsafe/caxa@3.0.6 caxa ...so we never touch the pnpm global bin path.Test plan
Build binariesworkflow withversion: v1.43.0-rc.3(workflow_dispatch) against this branch to verify amd64 + arm64 builds complete and the sanity-check binary step passes.lodestar devsmoke-test inside the artifact are unchanged.AI Assistance Disclosure
🤖 Generated with AI assistance