? Verifying lockfile against supply-chain policies (413 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +209 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 209, reused 0, downloaded 51, added 0 Packages are copied 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 209, reused 0, downloaded 155, added 8 Progress: resolved 209, reused 0, downloaded 209, added 209, done ✗ Lockfile failed supply-chain policy check (413 entries in 3.5s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 10 lockfile entries failed verification: @vue/compiler-core@3.5.41 was published at 2026-08-05T06:58:17.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) @vue/compiler-dom@3.5.41 was published at 2026-08-05T06:58:21.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) @vue/compiler-sfc@3.5.41 was published at 2026-08-05T06:58:25.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) @vue/compiler-ssr@3.5.41 was published at 2026-08-05T06:58:30.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) @vue/reactivity@3.5.41 was published at 2026-08-05T06:58:34.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) @vue/runtime-core@3.5.41 was published at 2026-08-05T06:58:37.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) @vue/runtime-dom@3.5.41 was published at 2026-08-05T06:58:41.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) @vue/server-renderer@3.5.41 was published at 2026-08-05T06:58:45.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) @vue/shared@3.5.41 was published at 2026-08-05T06:58:49.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) vue@3.5.41 was published at 2026-08-05T06:58:58.000Z, within the minimumReleaseAge cutoff (2026-08-05T01:59:37.264Z) 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.