? Verifying lockfile against supply-chain policies (338 entries)... ✗ Lockfile failed supply-chain policy check (338 entries in 1.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 12 lockfile entries failed verification: @vizejs/native-darwin-arm64@0.164.0 was published at 2026-06-03T02:53:44.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/native-darwin-x64@0.164.0 was published at 2026-06-03T02:54:05.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/native-linux-arm64-gnu@0.164.0 was published at 2026-06-03T02:54:27.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/native-linux-arm64-musl@0.164.0 was published at 2026-06-03T02:54:59.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/native-linux-x64-gnu@0.164.0 was published at 2026-06-03T02:55:20.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/native-linux-x64-musl@0.164.0 was published at 2026-06-03T02:55:41.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/native-win32-arm64-msvc@0.164.0 was published at 2026-06-03T02:56:03.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/native-win32-x64-msvc@0.164.0 was published at 2026-06-03T02:56:25.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/native@0.164.0 was published at 2026-06-03T02:56:46.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) @vizejs/vite-plugin@0.164.0 was published at 2026-06-03T02:58:26.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) oxlint-plugin-vize@0.164.0 was published at 2026-06-03T02:57:43.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) vize@0.164.0 was published at 2026-06-03T02:57:38.000Z, within the minimumReleaseAge cutoff (2026-06-02T05:10:48.516Z) 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.