Command "vp install" (cwd: /home/runner/work/vibe-dashboard/vibe-dashboard) exited with code 1

Scope: all 5 workspace projects ? Verifying lockfile against supply-chain policies (353 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +229 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Packages are hard linked from the content-addressable store to the virtual store. Content-addressable store is at: /home/runner/.local/share/pnpm/store/v11 Virtual store is at: node_modules/.pnpm Progress: resolved 229, reused 216, downloaded 7, added 17 Progress: resolved 229, reused 216, downloaded 10, added 229, done ✗ Lockfile failed supply-chain policy check (353 entries in 4.4s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 10 lockfile entries failed verification: @voidzero-dev/vite-plus-core@0.3.2 was published at 2026-09-14T14:58:01.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) @voidzero-dev/vite-plus-darwin-arm64@0.3.2 was published at 2026-09-14T14:53:00.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) @voidzero-dev/vite-plus-darwin-x64@0.3.2 was published at 2026-09-14T14:53:10.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) @voidzero-dev/vite-plus-linux-arm64-gnu@0.3.2 was published at 2026-09-14T14:53:18.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) @voidzero-dev/vite-plus-linux-arm64-musl@0.3.2 was published at 2026-09-14T14:53:25.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) @voidzero-dev/vite-plus-linux-x64-gnu@0.3.2 was published at 2026-09-14T14:53:33.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) @voidzero-dev/vite-plus-linux-x64-musl@0.3.2 was published at 2026-09-14T14:53:42.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) @voidzero-dev/vite-plus-win32-arm64-msvc@0.3.2 was published at 2026-09-14T14:53:49.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) @voidzero-dev/vite-plus-win32-x64-msvc@0.3.2 was published at 2026-09-14T14:53:57.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.681Z) vite-plus@0.3.2 was published at 2026-09-14T15:06:29.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:40:55.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.

Command "vp install" (cwd: /Users/runner/work/vibe-dashboard/vibe-dashboard) exited with code 1

Scope: all 5 workspace projects ? Verifying lockfile against supply-chain policies (353 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +230 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 230, reused 182, downloaded 0, added 0 Packages are cloned from the content-addressable store to the virtual store. Content-addressable store is at: /Users/runner/Library/pnpm/store/v11 Virtual store is at: node_modules/.pnpm Progress: resolved 230, reused 217, downloaded 5, added 3 Progress: resolved 230, reused 217, downloaded 10, added 5 ✗ Lockfile failed supply-chain policy check (353 entries in 3.9s) Progress: resolved 230, reused 217, downloaded 10, added 49 Progress: resolved 230, reused 217, downloaded 10, added 171 Progress: resolved 230, reused 217, downloaded 10, added 230, done [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 10 lockfile entries failed verification: @voidzero-dev/vite-plus-core@0.3.2 was published at 2026-09-14T14:58:01.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) @voidzero-dev/vite-plus-darwin-arm64@0.3.2 was published at 2026-09-14T14:53:00.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) @voidzero-dev/vite-plus-darwin-x64@0.3.2 was published at 2026-09-14T14:53:10.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) @voidzero-dev/vite-plus-linux-arm64-gnu@0.3.2 was published at 2026-09-14T14:53:18.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) @voidzero-dev/vite-plus-linux-arm64-musl@0.3.2 was published at 2026-09-14T14:53:25.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) @voidzero-dev/vite-plus-linux-x64-gnu@0.3.2 was published at 2026-09-14T14:53:33.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) @voidzero-dev/vite-plus-linux-x64-musl@0.3.2 was published at 2026-09-14T14:53:42.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) @voidzero-dev/vite-plus-win32-arm64-msvc@0.3.2 was published at 2026-09-14T14:53:49.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) @voidzero-dev/vite-plus-win32-x64-msvc@0.3.2 was published at 2026-09-14T14:53:57.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) vite-plus@0.3.2 was published at 2026-09-14T15:06:29.000Z, within the minimumReleaseAge cutoff (2026-09-13T15:41:19.721Z) 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.

Command "vp install" (cwd: D:\a\vibe-dashboard\vibe-dashboard) exited with code 1