? Verifying lockfile against supply-chain policies (469 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +256 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 256, reused 0, downloaded 8, added 0 Packages are hard linked from the content-addressable store to the virtual store. Content-addressable store is at: /home/runner/.local/share/pnpm/store/v11 Virtual store is at: node_modules/.pnpm Progress: resolved 256, reused 0, downloaded 86, added 4 Progress: resolved 256, reused 0, downloaded 232, added 16 Progress: resolved 256, reused 0, downloaded 256, added 256, done ✗ Lockfile failed supply-chain policy check (469 entries in 3.9s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 2 lockfile entries failed verification: vite-plus@0.2.7 was published at 2026-07-31T08:54:17.000Z, within the minimumReleaseAge cutoff (2026-07-30T09:04:11.203Z) vite@8.2.0 was published at 2026-07-30T12:02:04.000Z, within the minimumReleaseAge cutoff (2026-07-30T09:04:11.203Z) 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.