Skip to content

fix(ci): add packageManager so pnpm/action-setup@v4 resolves - #75

Merged
sebbsssss merged 1 commit into
stagingfrom
fix/ci-pnpm-packagemanager
Apr 18, 2026
Merged

fix(ci): add packageManager so pnpm/action-setup@v4 resolves#75
sebbsssss merged 1 commit into
stagingfrom
fix/ci-pnpm-packagemanager

Conversation

@sebbsssss

Copy link
Copy Markdown
Owner

Summary

CI was failing at the pnpm/action-setup@v4 step with:

Error: No pnpm version is specified.
Please specify it by one of the following ways:

  • in the GitHub Action config with the key "version"
  • in the package.json with the key "packageManager"

v4 of the action dropped the default that v3 had. Neither version: nor packageManager was set anywhere in the repo, so every push failed at step 3 (pnpm setup).

Fix: add "packageManager": "pnpm@10.18.1" to root package.json. Matches local (pnpm 10.18.1). Also helps corepack pick the right pnpm for new contributors locally.

Test plan

🤖 Generated with Claude Code

…ersion

pnpm/action-setup@v4 requires either a "version" input in the workflow
or a "packageManager" field in the root package.json. Neither was set,
so CI failed at the pnpm setup step with "No pnpm version is specified."

Using packageManager (matches local 10.18.1) unblocks CI without
touching the workflow file, and also helps corepack resolve the right
pnpm version for contributors locally.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@vercel

vercel Bot commented Apr 18, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
cluude Ready Ready Preview, Comment Apr 18, 2026 4:03pm

Request Review

@sebbsssss
sebbsssss merged commit a38b980 into staging Apr 18, 2026
3 checks passed
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