Repository navigation
verifyDepsBeforeRun rechecks an unchanged lockfile on every single-project command #16993
Description
pnpm version
12.14.0
Configuration
verify-deps-before-run=true
optimistic-repeat-install=trueSingle project, without pnpm-workspace.yaml.
Reproduction
pnpm install
touch pnpm-lock.yaml
pnpm exec node --version
pnpm exec node --versionExpected behavior
The first command verifies that the touched lockfile still matches the installed dependencies. The second command uses the mtime fast path.
Actual behavior
Both commands treat the lockfile as modified and repeat the content check. A successful single-project check does not advance lastValidatedTimestamp, although lockfile drift is measured against that timestamp.
Activity
github-actions commentedon Oct 16, 2026
@alitas, are you planning to open a pull request for this? If so, reply here and a maintainer will assign the issue to you, so nobody else starts on the same fix.
alitas commentedon Oct 16, 2026
Yes, I'm working on this and plan to open a pull request.
fix: settle single-project lockfile checks (pnpm#16996)
refactor(package-manager): share the content phase of the repeat-inst…
Update pnpm to v12.15.0 (#2046)
Update pnpm to v12.15.0 (#2046)