Skip to content

Update Vue packages to v3.5.35 #137

Update Vue packages to v3.5.35

Update Vue packages to v3.5.35 #137

Triggered via pull request May 28, 2026 00:40
Status Failure
Total duration 12s
Artifacts

typecheck.yml

on: pull_request
typecheck
10s
typecheck
Fit to window
Zoom out
Zoom in

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 (335 entries)... ✗ Lockfile failed supply-chain policy check (335 entries in 1.5s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 10 lockfile entries failed verification: @vue/compiler-core@3.5.35 was published at 2026-05-27T09:04:14.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) @vue/compiler-dom@3.5.35 was published at 2026-05-27T09:04:18.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) @vue/compiler-sfc@3.5.35 was published at 2026-05-27T09:04:23.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) @vue/compiler-ssr@3.5.35 was published at 2026-05-27T09:04:28.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) @vue/reactivity@3.5.35 was published at 2026-05-27T09:04:32.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) @vue/runtime-core@3.5.35 was published at 2026-05-27T09:04:36.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) @vue/runtime-dom@3.5.35 was published at 2026-05-27T09:04:40.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) @vue/server-renderer@3.5.35 was published at 2026-05-27T09:04:44.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) @vue/shared@3.5.35 was published at 2026-05-27T09:04:48.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) vue@3.5.35 was published at 2026-05-27T09:04:52.000Z, within the minimumReleaseAge cutoff (2026-05-27T00:40:26.681Z) 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.