Update Vue packages to v3.5.40 #1199
renovate[bot]Annotations
2 errors
|
lint
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 (370 entries)...
Lockfile is up to date, resolution step is skipped
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +204
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Progress: resolved 204, reused 0, downloaded 52, added 0
Progress: resolved 204, reused 0, downloaded 169, added 11
Progress: resolved 204, reused 0, downloaded 204, added 204, done
✗ Lockfile failed supply-chain policy check (370 entries in 3.5s)
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 10 lockfile entries failed verification:
@vue/compiler-core@3.5.40 was published at 2026-07-16T03:07:49.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
@vue/compiler-dom@3.5.40 was published at 2026-07-16T03:07:54.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
@vue/compiler-sfc@3.5.40 was published at 2026-07-16T03:07:59.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
@vue/compiler-ssr@3.5.40 was published at 2026-07-16T03:08:03.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
@vue/reactivity@3.5.40 was published at 2026-07-16T03:08:07.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
@vue/runtime-core@3.5.40 was published at 2026-07-16T03:08:11.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
@vue/runtime-dom@3.5.40 was published at 2026-07-16T03:08:16.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
@vue/server-renderer@3.5.40 was published at 2026-07-16T03:08:20.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
@vue/shared@3.5.40 was published at 2026-07-16T03:08:25.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
vue@3.5.40 was published at 2026-07-16T03:08:35.000Z, within the minimumReleaseAge cutoff (2026-07-15T05:12:03.844Z)
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.
|