Skip to content
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

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

Closed
tjx666 opened this issue May 15, 2023 · 0 comments · Fixed by #6574
Closed

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

tjx666 opened this issue May 15, 2023 · 0 comments · Fixed by #6574
Assignees

Comments

@tjx666
Copy link

tjx666 commented May 15, 2023

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants