Skip to content

ERR_PNPM_LOCKFILE_CONFIG_MISMATCH started happening with 10.24.0 but no diff is generated even when running pnpm install --no-frozen-lockfile #10258

@sapphi-red

Description

@sapphi-red

Verify latest release

  • I verified that the issue exists in the latest pnpm release

pnpm version

10.24.0

Which area(s) of pnpm are affected? (leave empty if unsure)

Lockfile

Link to the code that reproduces this issue or a replay of the bug

https://github.com/rolldown/rolldown/tree/55d8483037fd6f8d6d0887f842eba16ae0278634

Reproduction steps

  1. (probably) Have a cache generated in an older version (in our case it should be 10.23.0)
  2. run pnpm install --frozen-lockfile

Sorry that it's not an actual reproduction.

Describe the Bug

After upgrading to 10.24.0, ERR_PNPM_LOCKFILE_CONFIG_MISMATCH started happening on netlify.

1:32:56 PM: Installing npm packages using pnpm version 10.24.0
1:32:56 PM:  ERR_PNPM_LOCKFILE_CONFIG_MISMATCH  Cannot proceed with the frozen installation. The current "catalogs" configuration doesn't match the value found in the lockfile
1:32:56 PM: Update your lockfile using "pnpm install --no-frozen-lockfile"
1:32:56 PM: Error during pnpm install

full logs

But no diff is generated when I run pnpm install --no-frozen-lockfile locally.

Probably related to #10231

Expected Behavior

I expect the diff to be generated when running pnpm install --no-frozen-lockfile, or the error to not happen.

Which Node.js version are you using?

24.11.1

Which operating systems have you used?

  • macOS
  • Windows
  • Linux

If your OS is a Linux based, which one it is? (Include the version if relevant)

Ubuntu Noble 24.04

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No fields configured for Bug.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions