? Verifying lockfile against supply-chain policies (411 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +240 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 240, reused 0, downloaded 54, added 0 Progress: resolved 240, reused 0, downloaded 172, added 12 Progress: resolved 240, reused 0, downloaded 239, added 136 Progress: resolved 240, reused 0, downloaded 240, added 240, done ✗ Lockfile failed supply-chain policy check (411 entries in 3.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: vite@8.1.5 was published at 2026-07-16T06:51:09.000Z, within the minimumReleaseAge cutoff (2026-07-15T10:48:27.897Z) 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.