? Verifying lockfile against supply-chain policies (376 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +205 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 205, reused 0, downloaded 58, added 0 Progress: resolved 205, reused 0, downloaded 164, added 11 Progress: resolved 205, reused 0, downloaded 205, added 184 Progress: resolved 205, reused 0, downloaded 205, added 205, done ✗ Lockfile failed supply-chain policy check (376 entries in 3.5s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 10 lockfile entries failed verification: @vue/compiler-core@3.5.39 was published at 2026-06-25T09:43:08.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) @vue/compiler-dom@3.5.39 was published at 2026-06-25T09:43:13.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) @vue/compiler-sfc@3.5.39 was published at 2026-06-25T09:43:19.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) @vue/compiler-ssr@3.5.39 was published at 2026-06-25T09:43:23.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) @vue/reactivity@3.5.39 was published at 2026-06-25T09:43:29.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) @vue/runtime-core@3.5.39 was published at 2026-06-25T09:43:34.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) @vue/runtime-dom@3.5.39 was published at 2026-06-25T09:43:38.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) @vue/server-renderer@3.5.39 was published at 2026-06-25T09:43:43.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) @vue/shared@3.5.39 was published at 2026-06-25T09:43:48.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) vue@3.5.39 was published at 2026-06-25T09:43:59.000Z, within the minimumReleaseAge cutoff (2026-06-25T00:47:35.359Z) 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.