Skip to content

fix: add packageManager field for pnpm/action-setup@v4 - #2

Merged
maggit merged 3 commits into
mainfrom
fix/pnpm-version
Feb 8, 2026
Merged

fix: add packageManager field for pnpm/action-setup@v4#2
maggit merged 3 commits into
mainfrom
fix/pnpm-version

Conversation

@maggit

@maggit maggit commented Feb 8, 2026

Copy link
Copy Markdown
Owner

Summary

  • Adds "packageManager": "pnpm@10.28.2" to root package.json
  • Fixes pnpm/action-setup@v4 failing with "No pnpm version is specified" in both dry-run.yml and release-npm.yml workflows

Test plan

  • Verify the dry-run workflow passes on this PR
  • Confirm release-npm workflow will pick up the version on next tag push

🤖 Generated with Claude Code

maggit and others added 3 commits February 8, 2026 00:28
The pnpm/action-setup@v4 action requires a pnpm version to be specified
either in the action config or via the packageManager field in package.json.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
pnpm doesn't support --if-present like npm does. Removed the lint step
since no lint script exists, and removed --if-present from test/build
since those scripts do exist.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Tests depend on assets/ directory which is generated by the build step
(copy-assets.js). Also removed --if-present flags from release workflow
since pnpm doesn't support them.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@maggit
maggit merged commit 7ac560b into main Feb 8, 2026
1 check passed
@maggit
maggit deleted the fix/pnpm-version branch February 12, 2026 04:00
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