Skip to content
CI

chore(deps): update vite-plus and related packages to v0.1.24 #99

Sign in to view logs

chore(deps): update vite-plus and related packages to v0.1.24

chore(deps): update vite-plus and related packages to v0.1.24 #99

Re-run triggered June 2, 2026 00:26
@fengmk2fengmk2
#29
renovate/vite+
Status Failure
Total duration 23s
Artifacts –

ci.yml

on: pull_request
test
18s
test
staging-deploy
0s
staging-deploy
Fit to window
Zoom out
Zoom in

Annotations

2 errors
test
Command "vp install" (cwd: /home/runner/work/setup.viteplus.dev/setup.viteplus.dev) exited with code 1
vp install failed
? Verifying lockfile against supply-chain policies (381 entries)... ✗ Lockfile failed supply-chain policy check (381 entries in 2.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 11 lockfile entries failed verification: @voidzero-dev/vite-plus-core@0.1.24 was published at 2026-06-01T13:04:53.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-darwin-arm64@0.1.24 was published at 2026-06-01T13:03:11.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-darwin-x64@0.1.24 was published at 2026-06-01T13:03:19.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-linux-arm64-gnu@0.1.24 was published at 2026-06-01T13:03:27.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-linux-arm64-musl@0.1.24 was published at 2026-06-01T13:03:33.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-linux-x64-gnu@0.1.24 was published at 2026-06-01T13:03:40.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-linux-x64-musl@0.1.24 was published at 2026-06-01T13:03:47.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-test@0.1.24 was published at 2026-06-01T13:04:59.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-win32-arm64-msvc@0.1.24 was published at 2026-06-01T13:03:54.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) @voidzero-dev/vite-plus-win32-x64-msvc@0.1.24 was published at 2026-06-01T13:04:01.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) vite-plus@0.1.24 was published at 2026-06-01T13:05:06.000Z, within the minimumReleaseAge cutoff (2026-06-01T00:26:48.008Z) 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.