? 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 146, added 141 Progress: resolved 204, reused 0, downloaded 200, added 200 ✗ Lockfile failed supply-chain policy check (370 entries in 3s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 19 lockfile entries failed verification: @oxlint/binding-android-arm-eabi@1.76.0 was published at 2026-07-27T15:56:47.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-android-arm64@1.76.0 was published at 2026-07-27T15:56:17.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-darwin-arm64@1.76.0 was published at 2026-07-27T15:56:11.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-darwin-x64@1.76.0 was published at 2026-07-27T15:57:37.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-freebsd-x64@1.76.0 was published at 2026-07-27T15:57:49.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-arm-gnueabihf@1.76.0 was published at 2026-07-27T15:56:53.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-arm-musleabihf@1.76.0 was published at 2026-07-27T15:56:59.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-arm64-gnu@1.76.0 was published at 2026-07-27T15:56:29.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-arm64-musl@1.76.0 was published at 2026-07-27T15:56:35.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-ppc64-gnu@1.76.0 was published at 2026-07-27T15:57:12.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-riscv64-gnu@1.76.0 was published at 2026-07-27T15:57:18.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-riscv64-musl@1.76.0 was published at 2026-07-27T15:57:24.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-s390x-gnu@1.76.0 was published at 2026-07-27T15:57:31.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-x64-gnu@1.76.0 was published at 2026-07-27T15:57:55.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-linux-x64-musl@1.76.0 was published at 2026-07-27T15:58:01.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-openharmony-arm64@1.76.0 was published at 2026-07-27T15:56:41.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-win32-arm64-msvc@1.76.0 was published at 2026-07-27T15:56:23.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-win32-ia32-msvc@1.76.0 was published at 2026-07-27T15:57:05.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) @oxlint/binding-win32-x64-msvc@1.76.0 was published at 2026-07-27T15:57:43.000Z, within the minimumReleaseAge cutoff (2026-07-27T00:37:06.640Z) 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. Progress: resolved 204, reused 0, downloaded 203, added 203