ERR_PNPM_OUTDATED_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with package.json
pnpm’s lockfile doesn’t match package.json, and CI installs with a frozen lockfile.
Exact message you may see
is not up to date with package.json
Seen on:
npm
Meaning
The pnpm equivalent of npm ci being out of sync. Update the lockfile locally and commit it.
Common causes
- package.json changed without updating pnpm-lock.yaml
- Different pnpm versions locally and in CI
⚡ Quick fix
- Run pnpm install locally and commit the lockfile
- Pin the pnpm version (packageManager field)
Detailed fix by platform
npm
"packageManager": "pnpm@9.12.0"
How to diagnose
- Versions — pnpm -v locally vs CI
- Recent change — Did it start after a deploy, upgrade, or configuration change? Compare with the last working version.
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- AADSTS70021 AADSTS70021: No matching federated identity record found for presented assertion (GitHub Actions / workload identity)
- Command CodeSign failed Command CodeSign failed with a nonzero exit code (errSecInternalComponent / resource fork, Finder information not allowed)
- EINTEGRITY npm ERR! code EINTEGRITY — sha512 integrity checksum failed
Most viewed in npm
Other ways to find it
Where this error sits
Origin: Build & delivery. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Did this fix work for you?
Report a correction or suggest an improvement
Last updated 13 Oct 2026