ci(release): defer pnpm version to packageManager#95
Merged
Conversation
pnpm/action-setup@v6 errors out (ERR_PNPM_BAD_PM_VERSION) when both `version` and `packageManager` are set. The repo pins pnpm@10.15.1 in package.json, so drop the conflicting `version: 9` from release.yml and let the action read packageManager — matching how ci.yml already works via corepack. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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 Release workflow was failing at the Install pnpm step with
ERR_PNPM_BAD_PM_VERSION:pnpm/action-setup@v6treats this as fatal. Dropping the explicitversion: 9lets the action defer topackageManager— same single-source-of-truth patternci.ymlalready uses via corepack.Surfaced while triggering the v0.6.0 release (failed run).
Test plan
🤖 Generated with Claude Code