? Verifying lockfile against supply-chain policies (490 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +249 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 249, reused 237, downloaded 10, added 153 Progress: resolved 249, reused 237, downloaded 10, added 248, done ✗ Lockfile failed supply-chain policy check (490 entries in 11.3s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 2 lockfile entries failed verification: @vitest/mocker@5.0.0 was published at 2026-09-03T12:19:12.000Z, within the minimumReleaseAge cutoff (2026-09-02T14:09:36.156Z) @vitest/spy@5.0.0 was published at 2026-09-03T12:19:02.000Z, within the minimumReleaseAge cutoff (2026-09-02T14:09:36.156Z) The lockfile contains entries that the active policies reject. This can mean the lockfile is stale, or that someone committed a lockfile that bypassed the policy locally — inspect recent changes to pnpm-lock.yaml before trusting it. If the changes look expected, run "pnpm clean --lockfile" and then "pnpm install" to rebuild from a fresh resolution. Alternatively, relax the policy that flagged them.