? Verifying lockfile against supply-chain policies (333 entries)... ✗ Lockfile failed supply-chain policy check (333 entries in 2.1s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 32 lockfile entries failed verification: @oxlint/binding-android-arm-eabi@1.68.0 was published at 2026-06-01T17:06:31.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-android-arm64@1.68.0 was published at 2026-06-01T17:06:00.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-darwin-arm64@1.68.0 was published at 2026-06-01T17:05:55.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-darwin-x64@1.68.0 was published at 2026-06-01T17:07:19.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-freebsd-x64@1.68.0 was published at 2026-06-01T17:07:30.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-arm-gnueabihf@1.68.0 was published at 2026-06-01T17:06:37.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-arm-musleabihf@1.68.0 was published at 2026-06-01T17:06:43.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-arm64-gnu@1.68.0 was published at 2026-06-01T17:06:13.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-arm64-musl@1.68.0 was published at 2026-06-01T17:06:19.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-ppc64-gnu@1.68.0 was published at 2026-06-01T17:06:55.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-riscv64-gnu@1.68.0 was published at 2026-06-01T17:07:01.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-riscv64-musl@1.68.0 was published at 2026-06-01T17:07:06.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-s390x-gnu@1.68.0 was published at 2026-06-01T17:07:13.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-x64-gnu@1.68.0 was published at 2026-06-01T17:07:38.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-linux-x64-musl@1.68.0 was published at 2026-06-01T17:07:45.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-openharmony-arm64@1.68.0 was published at 2026-06-01T17:06:25.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-win32-arm64-msvc@1.68.0 was published at 2026-06-01T17:06:06.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-win32-ia32-msvc@1.68.0 was published at 2026-06-01T17:06:48.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @oxlint/binding-win32-x64-msvc@1.68.0 was published at 2026-06-01T17:07:25.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) @vizejs/native-darwin-arm64@0.163.0 was published at 2026-06-02T12:49:38.000Z, within the minimumReleaseAge cutoff (2026-06-01T16:01:23.823Z) …and 12 more 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.