? Verifying lockfile against supply-chain policies (371 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +200 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 200, reused 194, downloaded 4, added 198 Progress: resolved 200, reused 194, downloaded 6, added 200, done ✗ Lockfile failed supply-chain policy check (371 entries in 2.1s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 19 lockfile entries failed verification: @oxlint/binding-android-arm-eabi@1.71.0 was published at 2026-06-22T12:28:59.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-android-arm64@1.71.0 was published at 2026-06-22T12:28:27.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-darwin-arm64@1.71.0 was published at 2026-06-22T12:28:21.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-darwin-x64@1.71.0 was published at 2026-06-22T12:29:52.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-freebsd-x64@1.71.0 was published at 2026-06-22T12:30:04.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-arm-gnueabihf@1.71.0 was published at 2026-06-22T12:29:06.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-arm-musleabihf@1.71.0 was published at 2026-06-22T12:29:13.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-arm64-gnu@1.71.0 was published at 2026-06-22T12:28:40.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-arm64-musl@1.71.0 was published at 2026-06-22T12:28:46.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-ppc64-gnu@1.71.0 was published at 2026-06-22T12:29:26.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-riscv64-gnu@1.71.0 was published at 2026-06-22T12:29:33.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-riscv64-musl@1.71.0 was published at 2026-06-22T12:29:40.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-s390x-gnu@1.71.0 was published at 2026-06-22T12:29:47.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-x64-gnu@1.71.0 was published at 2026-06-22T12:30:12.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-linux-x64-musl@1.71.0 was published at 2026-06-22T12:30:20.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-openharmony-arm64@1.71.0 was published at 2026-06-22T12:28:53.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-win32-arm64-msvc@1.71.0 was published at 2026-06-22T12:28:34.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-win32-ia32-msvc@1.71.0 was published at 2026-06-22T12:29:19.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) @oxlint/binding-win32-x64-msvc@1.71.0 was published at 2026-06-22T12:29:58.000Z, within the minimumReleaseAge cutoff (2026-06-21T16:56:17.375Z) 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.