? Verifying lockfile against supply-chain policies (340 entries)... ✗ Lockfile failed supply-chain policy check (340 entries in 1.7s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 22 lockfile entries failed verification: @vizejs/native-darwin-arm64@0.131.0 was published at 2026-05-25T13:58:32.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-darwin-arm64@0.132.0 was published at 2026-05-25T16:58:02.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-darwin-x64@0.131.0 was published at 2026-05-25T13:58:53.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-darwin-x64@0.132.0 was published at 2026-05-25T16:58:24.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-linux-arm64-gnu@0.131.0 was published at 2026-05-25T13:59:14.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-linux-arm64-gnu@0.132.0 was published at 2026-05-25T16:58:46.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-linux-arm64-musl@0.131.0 was published at 2026-05-25T13:59:47.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-linux-arm64-musl@0.132.0 was published at 2026-05-25T16:59:07.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-linux-x64-gnu@0.131.0 was published at 2026-05-25T14:00:08.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-linux-x64-gnu@0.132.0 was published at 2026-05-25T16:59:40.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-linux-x64-musl@0.131.0 was published at 2026-05-25T14:00:40.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-linux-x64-musl@0.132.0 was published at 2026-05-25T17:00:13.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-win32-arm64-msvc@0.131.0 was published at 2026-05-25T14:01:02.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-win32-arm64-msvc@0.132.0 was published at 2026-05-25T17:00:35.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-win32-x64-msvc@0.131.0 was published at 2026-05-25T14:01:35.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native-win32-x64-msvc@0.132.0 was published at 2026-05-25T17:00:58.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native@0.131.0 was published at 2026-05-25T14:01:55.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/native@0.132.0 was published at 2026-05-25T17:01:19.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) @vizejs/vite-plugin@0.131.0 was published at 2026-05-25T14:03:27.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) oxlint-plugin-vize@0.132.0 was published at 2026-05-25T17:02:05.000Z, within the minimumReleaseAge cutoff (2026-05-24T17:03:17.767Z) …and 2 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.