fix(deps): use pnpm 7 not pnpm 8 (new latest) #855
Merged
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.
This PR remediates a breaking change caused by the release of pnpm 8.0.0 on March 28, 2023.
Problem
pnpm install --frozen-lockfile
does not acceptpnpm-lock.yaml
withlockfileVersion: 5.4
generated by pnpm v7.30.5.pnpm 8.0.0 is a breaking change. Apart from the compatibility issue with
lockfileVersion: 5.4
it also removes support for Node.js 14..github/workflows/example-basic-pnpm.yml uses pnpm/action-setup@v2
with: version: latest
Workaround
Bind pnpm/action-setup@v2 using
with: version: 7
.Related