Skip to content

lockfile is not latest but output Lockfile is up to date #6544

@tjx666

Description

@tjx666

pnpm version:

8.5.1

Code to reproduce the issue:

https://github.com/tjx666/npm-issue-lockfile

Expected behavior:

Don't output Lockfile is up to date, resolution step is skipped

Actual behavior:

check github action here: https://github.com/tjx666/npm-issue-lockfile/actions/runs/4978673250/jobs/8909277167

Lockfile is up to date, resolution step is skipped
 ERR_PNPM_OUTDATED_LOCKFILE  Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json

Note that in CI environments this setting is true by default. If you still need to run install in such cases, use "pnpm install --no-frozen-lockfile"

Failure reason:
specifiers in the lockfile ({"lodash":"^4.1[7](https://github.com/tjx666/npm-issue-lockfile/actions/runs/4978673250/jobs/8909277167#step:7:8).21"}) don't match specs in package.json ({"lodash":"4.17.20"})
Error: Process completed with exit code 1.

Additional information:

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

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions