Skip to content

pnpm i followed by pnpm i --frozen-lockfile complains about outdated lockfile #5080

@JonnyBurger

Description

@JonnyBurger

We have managed to land in a state where pnpm i --frozen-lockfile compains that pnpm-lock.yaml is not up to date, but pnpm i does not fix it. This issue appeared since the latest release.

pnpm version:

v7.6.0

Code to reproduce the issue:

git clone https://github.com/remotion-dev/remotion remotion-pnpm
cd remotion-pnpm
git checkout f76e74cec19d80348813760ca053a4af83ab71bc
pnpm i
pnpm i --frozen-lockfile

Expected behavior:

No error

Actual behavior:

 ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up-to-date with packages/core/package.json

Additional information:

Corepack is enabled
The original lockfile was generated by v7.2.1

  • node -v prints: v16.16.0
  • Windows, macOS, or Linux?: macOS

Metadata

Metadata

Assignees

Labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions