Update Vize packages #179
Annotations
2 errors
|
typecheck
Command "vp install" (cwd: /home/runner/work/vuefes-japan-speakers/vuefes-japan-speakers) exited with code 1
|
|
vp install failed
? Verifying lockfile against supply-chain policies (346 entries)...
✗ Lockfile failed supply-chain policy check (346 entries in 1.7s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 12 lockfile entries failed verification:
@vizejs/native-darwin-arm64@0.166.0 was published at 2026-06-03T11:45:12.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/native-darwin-x64@0.166.0 was published at 2026-06-03T11:45:33.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/native-linux-arm64-gnu@0.166.0 was published at 2026-06-03T11:46:03.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/native-linux-arm64-musl@0.166.0 was published at 2026-06-03T11:46:36.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/native-linux-x64-gnu@0.166.0 was published at 2026-06-03T11:47:07.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/native-linux-x64-musl@0.166.0 was published at 2026-06-03T11:47:40.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/native-win32-arm64-msvc@0.166.0 was published at 2026-06-03T11:48:00.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/native-win32-x64-msvc@0.166.0 was published at 2026-06-03T11:48:21.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/native@0.166.0 was published at 2026-06-03T11:48:42.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
@vizejs/vite-plugin@0.166.0 was published at 2026-06-03T11:50:17.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
oxlint-plugin-vize@0.166.0 was published at 2026-06-03T11:49:47.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
vize@0.166.0 was published at 2026-06-03T11:49:37.000Z, within the minimumReleaseAge cutoff (2026-06-02T14:39:41.352Z)
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.
|