? Verifying lockfile against supply-chain policies (327 entries)... ✗ Lockfile failed supply-chain policy check (327 entries in 1.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 12 lockfile entries failed verification: @vizejs/native-darwin-arm64@0.107.0 was published at 2026-05-18T12:41:24.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/native-darwin-x64@0.107.0 was published at 2026-05-18T12:41:56.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/native-linux-arm64-gnu@0.107.0 was published at 2026-05-18T12:42:24.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/native-linux-arm64-musl@0.107.0 was published at 2026-05-18T12:42:48.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/native-linux-x64-gnu@0.107.0 was published at 2026-05-18T12:43:17.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/native-linux-x64-musl@0.107.0 was published at 2026-05-18T12:43:41.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/native-win32-arm64-msvc@0.107.0 was published at 2026-05-18T12:44:11.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/native-win32-x64-msvc@0.107.0 was published at 2026-05-18T12:44:44.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/native@0.107.0 was published at 2026-05-18T12:45:13.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) @vizejs/vite-plugin@0.107.0 was published at 2026-05-18T12:46:50.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) oxlint-plugin-vize@0.107.0 was published at 2026-05-18T12:46:05.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) vize@0.107.0 was published at 2026-05-18T12:46:06.000Z, within the minimumReleaseAge cutoff (2026-05-18T00:24:19.384Z) 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.