? Verifying lockfile against supply-chain policies (369 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +203 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 203, reused 0, downloaded 54, added 0 Progress: resolved 203, reused 0, downloaded 169, added 12 Progress: resolved 203, reused 0, downloaded 203, added 203, done ✗ Lockfile failed supply-chain policy check (369 entries in 3.3s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 19 lockfile entries failed verification: @oxlint/binding-android-arm-eabi@1.73.0 was published at 2026-07-06T23:05:56.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-android-arm64@1.73.0 was published at 2026-07-06T23:05:24.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-darwin-arm64@1.73.0 was published at 2026-07-06T23:05:16.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-darwin-x64@1.73.0 was published at 2026-07-06T23:06:50.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-freebsd-x64@1.73.0 was published at 2026-07-06T23:07:03.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-arm-gnueabihf@1.73.0 was published at 2026-07-06T23:06:02.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-arm-musleabihf@1.73.0 was published at 2026-07-06T23:06:08.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-arm64-gnu@1.73.0 was published at 2026-07-06T23:05:37.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-arm64-musl@1.73.0 was published at 2026-07-06T23:05:43.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-ppc64-gnu@1.73.0 was published at 2026-07-06T23:06:21.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-riscv64-gnu@1.73.0 was published at 2026-07-06T23:06:28.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-riscv64-musl@1.73.0 was published at 2026-07-06T23:06:35.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-s390x-gnu@1.73.0 was published at 2026-07-06T23:06:43.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-x64-gnu@1.73.0 was published at 2026-07-06T23:07:09.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-linux-x64-musl@1.73.0 was published at 2026-07-06T23:07:16.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-openharmony-arm64@1.73.0 was published at 2026-07-06T23:05:50.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-win32-arm64-msvc@1.73.0 was published at 2026-07-06T23:05:30.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-win32-ia32-msvc@1.73.0 was published at 2026-07-06T23:06:14.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) @oxlint/binding-win32-x64-msvc@1.73.0 was published at 2026-07-06T23:06:56.000Z, within the minimumReleaseAge cutoff (2026-07-06T17:32:55.257Z) 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.