regression with version 7.4.0, it no longer update pnpm-lock.yaml in CI due to recent PR to exit early on lockfile-only

[ghiscoding]

pnpm version:

7.4.0

Code to reproduce the issue:

see Lerna-Lite issue and it works fine with previous version 7.3.0. By looking at the recent PR #4932, which caused the regression, I found out that calling --fix-lockfile would make it work with the same behavior as before. Basically I used the fix lock file just because that seems to be the last flag I can use that is still in the if condition that was modified recently by PR #4932

pnpm/packages/core/src/install/index.ts

Lines 266 to 271 in 487527d

	if (
	!ctx.lockfileHadConflicts &&
	!opts.update &&
	!opts.fixLockfile &&
	installsOnly &&
	(

Expected behavior:

calling pnpm install --lockfile-only should work in CI and update lock file as it used to.

Actual behavior:

since latest release 7.4.0 it no longer update pnpm-lock.yaml in CI due to recent PR to exit early on lockfile-only

Temporary fix:

For now I'm adding the fix lock to get around the regression problem but it's not a viable solution and I hope the regression is fix soon.

# temp fix to go around the regression
pnpm install --lockfile-only --fix-lockfile

Additional information:

• node -v prints: all
• Windows, macOS, or Linux?: all

[zkochan]

I see, try pnpm install --lockfile-only --no-frozen-lockfile

[ghiscoding]

yes it does seem to help at least now the unit tests that were failing with 7.4.0 are now passing in CI, is that what you suggest to use all the time? I won't close the issue just yet but I can test it out with a new version bump and release of Lerna-Lite itself since I use pnpm in it as well, I'll do that in the next couple of hours. It does seem promising at least

[zkochan]

It should work with no changes when I release this fix: #4955

[ghiscoding]

oh that'd be great, do you have an ETA (estimated time) for a fix and new release of pnpm then?

[zkochan]

Probably in the next 24 hours.