? Verifying lockfile against supply-chain policies (335 entries)... ✗ Lockfile failed supply-chain policy check (335 entries in 1.8s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 12 lockfile entries failed verification: @vizejs/native-darwin-arm64@0.140.0 was published at 2026-05-28T14:11:38.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/native-darwin-x64@0.140.0 was published at 2026-05-28T14:12:12.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/native-linux-arm64-gnu@0.140.0 was published at 2026-05-28T14:12:34.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/native-linux-arm64-musl@0.140.0 was published at 2026-05-28T14:12:55.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/native-linux-x64-gnu@0.140.0 was published at 2026-05-28T14:13:28.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/native-linux-x64-musl@0.140.0 was published at 2026-05-28T14:13:59.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/native-win32-arm64-msvc@0.140.0 was published at 2026-05-28T14:14:21.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/native-win32-x64-msvc@0.140.0 was published at 2026-05-28T14:14:44.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/native@0.140.0 was published at 2026-05-28T14:15:04.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) @vizejs/vite-plugin@0.140.0 was published at 2026-05-28T14:16:50.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) oxlint-plugin-vize@0.140.0 was published at 2026-05-28T14:15:51.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) vize@0.140.0 was published at 2026-05-28T14:15:57.000Z, within the minimumReleaseAge cutoff (2026-05-27T21:01:40.824Z) 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.