? Verifying lockfile against supply-chain policies (322 entries)... ✗ Lockfile failed supply-chain policy check (322 entries in 2s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 12 lockfile entries failed verification: @vizejs/native-darwin-arm64@0.113.0 was published at 2026-05-20T14:11:51.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/native-darwin-x64@0.113.0 was published at 2026-05-20T14:12:14.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/native-linux-arm64-gnu@0.113.0 was published at 2026-05-20T14:12:36.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/native-linux-arm64-musl@0.113.0 was published at 2026-05-20T14:12:58.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/native-linux-x64-gnu@0.113.0 was published at 2026-05-20T14:13:22.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/native-linux-x64-musl@0.113.0 was published at 2026-05-20T14:13:45.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/native-win32-arm64-msvc@0.113.0 was published at 2026-05-20T14:14:18.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/native-win32-x64-msvc@0.113.0 was published at 2026-05-20T14:14:40.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/native@0.113.0 was published at 2026-05-20T14:15:01.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) @vizejs/vite-plugin@0.113.0 was published at 2026-05-20T14:17:15.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) oxlint-plugin-vize@0.113.0 was published at 2026-05-20T14:16:08.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) vize@0.113.0 was published at 2026-05-20T14:16:21.000Z, within the minimumReleaseAge cutoff (2026-05-19T14:41:11.056Z) 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.