? Verifying lockfile against supply-chain policies (327 entries)... ✗ Lockfile failed supply-chain policy check (327 entries in 1.5s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 12 lockfile entries failed verification: @vizejs/native-darwin-arm64@0.114.0 was published at 2026-05-20T15:14:36.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/native-darwin-x64@0.114.0 was published at 2026-05-20T15:14:58.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/native-linux-arm64-gnu@0.114.0 was published at 2026-05-20T15:15:19.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/native-linux-arm64-musl@0.114.0 was published at 2026-05-20T15:15:51.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/native-linux-x64-gnu@0.114.0 was published at 2026-05-20T15:16:14.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/native-linux-x64-musl@0.114.0 was published at 2026-05-20T15:16:35.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/native-win32-arm64-msvc@0.114.0 was published at 2026-05-20T15:16:57.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/native-win32-x64-msvc@0.114.0 was published at 2026-05-20T15:17:19.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/native@0.114.0 was published at 2026-05-20T15:17:39.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) @vizejs/vite-plugin@0.114.0 was published at 2026-05-20T15:19:21.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) oxlint-plugin-vize@0.114.0 was published at 2026-05-20T15:18:30.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) vize@0.114.0 was published at 2026-05-20T15:18:23.000Z, within the minimumReleaseAge cutoff (2026-05-20T10:54:21.080Z) 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.