fix: run pnpm install to fix the lockfile #5585
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.
I noticed that the pnpm lockfile is broken on the
v-next
currently. This is likely because I merged #5574 which brought inmain
intov-next
so it naturally had a lot of changes (including having to rewrite pnpm lock) and then #5541 got merged which likely got tested before and, later, the conflict was too obscure for GitHub to notice.To fix the lockfile, I just ran
pnpm install
in the root.