fix(ci): bump pnpm/action-setup v6.0.0 → v6.0.8 (upstream bootstrap bug fixed)#449
Merged
Merged
Conversation
…_PNPM_BROKEN_LOCKFILE pnpm/action-setup v6.0.0 bootstraps with pnpm 11.0.0-rc.0 and skips the self-update step when packageManager is set in package.json (returns undefined). This causes pnpm 11-rc to run pnpm install against a lockfile generated by pnpm 10, leading to ERR_PNPM_BROKEN_LOCKFILE. v4.4.0 correctly reads the packageManager field and installs the exact version specified (e.g. pnpm@10.28.0), which is compatible with the lockfileVersion 9.0.
The v6.0.0–v6.0.6 self-update bootstrap bug (pnpm/action-setup#256) that caused ERR_PNPM_BROKEN_LOCKFILE when `packageManager` is set in package.json has been fixed upstream in v6.0.7 and polished in v6.0.8 (released 2026-05-12). Replace the v4.4.0 workaround with the real fix. Ref: pnpm/action-setup#256 Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
MarvinZeising
changed the title
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Problem
All `Automatic Release` runs in repos using `template_changeset_release.yml` have been failing since v13.1.0 was adopted (May 8).
Error:
```
ERR_PNPM_BROKEN_LOCKFILE The lockfile at "pnpm-lock.yaml" is broken: expected a single document in the stream, but found more
```
Root Cause
`pnpm/action-setup@v6.0.0` (SHA `08c4be7e`) introduced a new bootstrap mechanism that:
This is a bug in `pnpm/action-setup` v6.0.0–v6.0.6, fixed upstream in pnpm/action-setup#256 and released as v6.0.7 (further polished in v6.0.8, released 2026-05-12).
Fix
Bump `pnpm/action-setup` to v6.0.8 (commit `0e279bb9`), which correctly handles the `packageManager` field in `package.json` and installs the pinned version instead of staying on the bootstrap pnpm 11-rc.
This is a proper upstream fix — no workaround needed.
Verification
Follow-up
After this is merged and tagged as a new release, consumers will need their `release.yml` updated to reference the new tag.