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

pnpm@7.7.1 - pnpm generates different lockfile locally and on CI #5124

Closed
dangreen opened this issue Jul 30, 2022 · 0 comments · Fixed by #5126
Closed

pnpm@7.7.1 - pnpm generates different lockfile locally and on CI #5124

dangreen opened this issue Jul 30, 2022 · 0 comments · Fixed by #5126
Assignees
Milestone

Comments

@dangreen
Copy link
Contributor

dangreen commented Jul 30, 2022

pnpm version:

7.7.0
7.7.1

Code to reproduce the issue:

https://github.com/gionkunz/chartist-js

Expected behavior:

successful dependencies installation

Actual behavior:

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"

Additional information:

v7.5.0 works perfect

v7.7.1 installed local and on CI, locally lockfile was updated and pushed, but on CI it still shows that lockfile is not up-to-date with package.json.

@zkochan zkochan self-assigned this Jul 30, 2022
zkochan added a commit that referenced this issue Jul 30, 2022
when the package has a publishConfig.directory field

close #5124
zkochan added a commit that referenced this issue Jul 30, 2022
when the package has a publishConfig.directory field

close #5124
@zkochan zkochan added this to the v7.8 milestone Sep 2, 2022
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