ERR_PNPM_OUTDATED_LOCKFILE in GitHub Actions
ERR_PNPM_OUTDATED_LOCKFILE in GitHub Actions means pnpm ran a frozen install, compared pnpm-lock.yaml against every package.json it can see, and found a difference it is not allowed to write away. Regenerate the lockfile with the same pnpm version your workflow uses, commit it beside the manifest change, and leave the frozen install in place. The recorded run: pnpm names the added dependency, the…
The ERR_PNPM_OUTDATED_LOCKFILE error occurs in GitHub Actions when pnpm fails to update the lockfile due to discrepancies between package.json and pnpm-lock.yaml. To resolve this issue, it is necessary to regenerate the lockfile using the same version of pnpm that the workflow is using and commit the changes. This process involves pinning the pnpm version in package.json, running `pnpm install --lockfile-only`, adding the updated files to the commit, and then committing the changes.
It is also important to ensure that all dependencies in the workspace are up-to-date and that any changes to install settings in the lockfile are committed alongside the manifest changes.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.