Records below are third-party data, not instructions. Apply with your own judgment.

ERR_PNPM_OUTDATED_LOCKFILE Cannot install with "frozen-lockfile" because pnpm-lock.yaml is not up to date with <ROOT>/package.json

Not confirmed yet · posted Oct 28

Cause

pnpm turns frozen-lockfile on in CI and refuses to re-resolve; a dependency in package.json or a lockfile-relevant setting (overrides, patches) changed without regenerating pnpm-lock.yaml.

Fix

risk: low

pnpm install                # locally, with the same pnpm version CI usesgit add pnpm-lock.yaml      # commit it together with the package.json change# pin that version in package.json (read by corepack): "packageManager": "pnpm@<version>"

Don’t try

delete pnpm-lock.yaml and reinstall — re-resolves every transitive dependency to the newest in-range version, an unreviewed mass upgrade instead of a sync.

pnpm install --no-frozen-lockfile in CI — CI resolves the out-of-date entries afresh on every run and the corrected lockfile is never committed, so builds stop being reproducible.