? Verifying lockfile against supply-chain policies (370 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +204 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 204, reused 0, downloaded 56, added 0 Progress: resolved 204, reused 0, downloaded 191, added 12 Progress: resolved 204, reused 0, downloaded 204, added 204, done ✗ Lockfile failed supply-chain policy check (370 entries in 3.4s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 19 lockfile entries failed verification: @oxlint/binding-android-arm-eabi@1.75.0 was published at 2026-07-21T23:19:02.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-android-arm64@1.75.0 was published at 2026-07-21T23:18:01.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-darwin-arm64@1.75.0 was published at 2026-07-21T23:17:49.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-darwin-x64@1.75.0 was published at 2026-07-21T23:20:21.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-freebsd-x64@1.75.0 was published at 2026-07-21T23:20:38.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-arm-gnueabihf@1.75.0 was published at 2026-07-21T23:19:15.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-arm-musleabihf@1.75.0 was published at 2026-07-21T23:19:26.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-arm64-gnu@1.75.0 was published at 2026-07-21T23:18:31.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-arm64-musl@1.75.0 was published at 2026-07-21T23:18:41.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-ppc64-gnu@1.75.0 was published at 2026-07-21T23:19:48.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-riscv64-gnu@1.75.0 was published at 2026-07-21T23:19:56.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-riscv64-musl@1.75.0 was published at 2026-07-21T23:20:04.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-s390x-gnu@1.75.0 was published at 2026-07-21T23:20:13.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-x64-gnu@1.75.0 was published at 2026-07-21T23:20:51.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-linux-x64-musl@1.75.0 was published at 2026-07-21T23:21:06.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-openharmony-arm64@1.75.0 was published at 2026-07-21T23:18:49.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-win32-arm64-msvc@1.75.0 was published at 2026-07-21T23:18:16.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-win32-ia32-msvc@1.75.0 was published at 2026-07-21T23:19:41.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) @oxlint/binding-win32-x64-msvc@1.75.0 was published at 2026-07-21T23:20:31.000Z, within the minimumReleaseAge cutoff (2026-07-20T23:32:10.831Z) 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.