fix(version): --sync-workspace-lock
flag no longer work because of pnpm regression
#233
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.
Description
Last version of pnpm v7.4.0 has a change to exit early on
install --lockfile-only
and that is impacting (aka failing) theversion
unit tests which use pnpm, it seems to be exiting too early and skipping the lock file update which defeat the purpose of the--sync-workspace-lock
flag.Adding
--fix-lockfile
to pnpm seems to be help to get previous pnpm behavior. I wish that--lockfile-only
would still work but the--fix-lockfile
flag is a quick fix for now until pnpm addresses this regression issue that I opened in the pnpm project.quick (patch) fix for issue #234
Motivation and Context
re-enable previously failing unit tests with pnpm and find a way to bypass new pnpm regression caused in latest pnpm 7.4.0
How Has This Been Tested?
unit tests
Types of changes
Checklist: