? Verifying lockfile against supply-chain policies (368 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +202 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 202, reused 0, downloaded 50, added 0 Progress: resolved 202, reused 0, downloaded 177, added 12 Progress: resolved 202, reused 0, downloaded 202, added 202, done ✗ Lockfile failed supply-chain policy check (368 entries in 3.2s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 19 lockfile entries failed verification: @oxlint/binding-android-arm-eabi@1.72.0 was published at 2026-06-29T23:09:21.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-android-arm64@1.72.0 was published at 2026-06-29T23:08:49.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-darwin-arm64@1.72.0 was published at 2026-06-29T23:08:43.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-darwin-x64@1.72.0 was published at 2026-06-29T23:10:12.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-freebsd-x64@1.72.0 was published at 2026-06-29T23:10:26.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-arm-gnueabihf@1.72.0 was published at 2026-06-29T23:09:27.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-arm-musleabihf@1.72.0 was published at 2026-06-29T23:09:32.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-arm64-gnu@1.72.0 was published at 2026-06-29T23:09:02.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-arm64-musl@1.72.0 was published at 2026-06-29T23:09:09.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-ppc64-gnu@1.72.0 was published at 2026-06-29T23:09:46.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-riscv64-gnu@1.72.0 was published at 2026-06-29T23:09:52.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-riscv64-musl@1.72.0 was published at 2026-06-29T23:09:59.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-s390x-gnu@1.72.0 was published at 2026-06-29T23:10:06.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-x64-gnu@1.72.0 was published at 2026-06-29T23:10:32.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-linux-x64-musl@1.72.0 was published at 2026-06-29T23:10:40.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-openharmony-arm64@1.72.0 was published at 2026-06-29T23:09:16.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-win32-arm64-msvc@1.72.0 was published at 2026-06-29T23:08:56.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-win32-ia32-msvc@1.72.0 was published at 2026-06-29T23:09:39.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) @oxlint/binding-win32-x64-msvc@1.72.0 was published at 2026-06-29T23:10:19.000Z, within the minimumReleaseAge cutoff (2026-06-29T13:04:33.948Z) 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.