New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting a lockfile config mismatch after upgrading to version 8.6.1 #6649
Comments
I assume the lockfile was created with pnpm v7, which has
Then update the lockfile. The lockfile generated with |
Similar Issue: pnpm/pnpm#6649
* chore: update changelog generator * chore: use pnpm to run auto-changelog from store * fix: ci error with a change in pnpm version Similar Issue: pnpm/pnpm#6649 * ci: support pnpm version 8 with the right lockfile config
ref: pnpm/pnpm#6649 (comment) Signed-off-by: Teakowa <27560638+Teakowa@users.noreply.github.com>
CI currently fails with a mention about the lockfile setting settings.autoInstallPeers Read more here: pnpm/pnpm#6649
CI currently fails with a mention about the lockfile setting settings.autoInstallPeers Read more here: pnpm/pnpm#6649
For macOS users affected by this who have upgraded through various versions but cannot find the source of the |
pnpm version:
8.6.1
Code to reproduce the issue:
updated from
8.5.1
tot8.6.1
then runpnpm install
Expected behavior:
No config mismatch
Actual behavior:
ERR_PNPM_LOCKFILE_CONFIG_MISMATCH Cannot proceed with the frozen installation. The current "settings.autoInstallPeers" configuration doesn't match the value found in the lockfile
after removing the section
settings
in the lock file it works again but this is not what I want to do manually.Additional information:
node -v
prints:v16.4.0
Linux
The text was updated successfully, but these errors were encountered: