pnpm: Frozen lockfile error despite up to date lockfile

pnpm version: 8.0.0 (though 7.30 seems also affected)

Running pnpm install --frozen-lockfile yields:

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

Now when I run pnpm install, there are no lockfile changes.

Interestingly enough this also happens:

❯ pnpm cache
 ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL  Command failed with ENOENT: cache
spawn cache ENOENT

I don’t have a repro, because I’m somewhat sure that this is my system being bonked, but I also could not find any guides for doing a clean uninstall (I tried store pruning, resetted all the configs etc)

Additional information:

node -v prints: v18.13.0
Windows, macOS, or Linux?: macOS Ventura 13.0

About this issue

Original URL
State: open
Created a year ago
Reactions: 11
Comments: 21 (5 by maintainers)

Commits related to this issue

feat: include some settings as fields in the lockfile ref #6312 — committed to pnpm/pnpm by zkochan a year ago
feat: include some settings as fields in the lockfile ref #6312 — committed to pnpm/pnpm by zkochan a year ago
feat: include some settings as fields in the lockfile ref #6312 — committed to pnpm/pnpm by zkochan a year ago
feat: include some settings as fields in the lockfile (#6557) ref #6312 — committed to pnpm/pnpm by zkochan a year ago
feat: include some settings as fields in the lockfile (#6557) ref #6312 close #6609 — committed to pnpm/pnpm by zkochan a year ago
feat: include some settings as fields in the lockfile (#6611) ref #6312 close #6609 — committed to pnpm/pnpm by zkochan a year ago
Improved error formatting Technical Change Notes ====================== This now uses GitHub `core.summary`. See the [job summaries][] blog post. There are some changes caused by annoying upgrades:... — committed to KineticCafe/actions-dco by halostatue a year ago
Improved error formatting Technical Change Notes ====================== This now uses GitHub `core.summary`. See the [job summaries][] blog post. There are some changes caused by annoying upgrades:... — committed to KineticCafe/actions-dco by halostatue a year ago

Most upvoted comments

Just upgraded lockfileVersion in pnpm.lock.yaml from 6.0 to 8.5.1 and boom, deployed successfully

MehdiRazaNaqvi on Nov 5, 2023

How did y’all upgrade the lockfile version? I’m running 8.15.2 and it is still generates a lockfile version 6. We are using pnpm on the latest MacOS

Just manually change the version number

chandramuralis on Feb 23, 2024

My problem is not why lock file is not latest. My problem is why pnpm output:

Lockfile is up to date, resolution step is skipped

@zkochan

tjx666 on May 14, 2023

Updating to pnpm@8.5.1 and re-installing deps resolved this for me.

justintemps on May 26, 2023

can confirm upgrading to 8 on a mac causes this issue when it is run in linux

pnpm config set auto-install-peers false used this command on the mac to fix the issue

i-bajrai on May 18, 2023

I understand what is your problem but I can’t fix it if I can’t reproduce it. You should provide steps to reproduce. If not, with more info in the error message maybe we’ll be able to figure out the issue.

zkochan on May 14, 2023

Try downgrading PNPM to v7 or upgrade the lockfile to v8

iamchathu on Mar 29, 2023