? Verifying lockfile against supply-chain policies (313 entries)... ✗ Lockfile failed supply-chain policy check (313 entries in 1.9s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 12 lockfile entries failed verification: @vizejs/native-darwin-arm64@0.153.0 was published at 2026-05-31T14:21:16.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/native-darwin-x64@0.153.0 was published at 2026-05-31T14:21:36.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/native-linux-arm64-gnu@0.153.0 was published at 2026-05-31T14:22:07.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/native-linux-arm64-musl@0.153.0 was published at 2026-05-31T14:22:26.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/native-linux-x64-gnu@0.153.0 was published at 2026-05-31T14:22:46.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/native-linux-x64-musl@0.153.0 was published at 2026-05-31T14:23:05.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/native-win32-arm64-msvc@0.153.0 was published at 2026-05-31T14:23:35.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/native-win32-x64-msvc@0.153.0 was published at 2026-05-31T14:23:55.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/native@0.153.0 was published at 2026-05-31T14:24:24.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) @vizejs/vite-plugin@0.153.0 was published at 2026-05-31T14:25:52.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) oxlint-plugin-vize@0.153.0 was published at 2026-05-31T14:25:13.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) vize@0.153.0 was published at 2026-05-31T14:25:07.000Z, within the minimumReleaseAge cutoff (2026-05-30T17:25:14.049Z) 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.