Scope: all 126 workspace projects ? Verifying lockfile against supply-chain policies (2076 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +1849 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 1849, reused 676, downloaded 0, added 0 Progress: resolved 1849, reused 1752, downloaded 1, added 1 Progress: resolved 1849, reused 1752, downloaded 72, added 60 Progress: resolved 1849, reused 1752, downloaded 72, added 302 Progress: resolved 1849, reused 1752, downloaded 72, added 539 Progress: resolved 1849, reused 1752, downloaded 72, added 800 Progress: resolved 1849, reused 1752, downloaded 72, added 1003 Progress: resolved 1849, reused 1752, downloaded 72, added 1092 Progress: resolved 1849, reused 1752, downloaded 72, added 1289 Progress: resolved 1849, reused 1752, downloaded 72, added 1433 ✗ Lockfile failed supply-chain policy check (2076 entries in 10.4s) Progress: resolved 1849, reused 1752, downloaded 72, added 1848 Progress: resolved 1849, reused 1752, downloaded 72, added 1849, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 2 lockfile entries failed verification: baseline-browser-mapping@2.11.21 was published at 2026-09-03T17:36:15.000Z, within the minimumReleaseAge cutoff (2026-09-03T15:50:49.257Z) electron-to-chromium@1.5.422 was published at 2026-09-04T06:07:39.000Z, within the minimumReleaseAge cutoff (2026-09-03T15:50:49.257Z) 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.