Skip to content

fix(ci): resolve pnpm/action-setup version conflict#83

Merged
NathanFlurry merged 1 commit into
mainfrom
fix/ci-pnpm-version
Jun 19, 2026
Merged

fix(ci): resolve pnpm/action-setup version conflict#83
NathanFlurry merged 1 commit into
mainfrom
fix/ci-pnpm-version

Conversation

@NathanFlurry

@NathanFlurry NathanFlurry commented Jun 19, 2026

Copy link
Copy Markdown
Member

Problem

CI fails on every commit (including main) at the pnpm/action-setup step, before any build runs:

ERR_PNPM_BAD_PM_VERSION  Multiple versions of pnpm specified

pnpm/action-setup@v4 refuses to run when the pnpm version is specified in two places:

  1. .github/workflows/ci.yml — the action's version: latest input
  2. root package.json"packageManager": "[email protected]"

When both are present, the action errors out rather than guessing which to honor.

Fix

Remove the version: input from the pnpm/action-setup step in ci.yml so the action reads the version solely from packageManager in package.json — the recommended single-source-of-truth configuration.

       - uses: pnpm/action-setup@v4
-        with:
-          version: latest
       - uses: actions/setup-node@v4

This un-breaks CI repo-wide.

Notes

  • The publish.yaml workflow's pnpm/action-setup steps already have no version: input, so they were never affected and are left untouched.
  • There is no .npmrc or other competing pnpm-version source; packageManager is now the only place the version is declared.

@railway-app

railway-app Bot commented Jun 19, 2026

Copy link
Copy Markdown

🚅 Environment secure-exec-pr-83 in rivet-frontend has no services deployed.

@NathanFlurry
NathanFlurry merged commit 7b0ba31 into main Jun 19, 2026
1 check failed
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.

1 participant