Command "sfw vp install" (cwd: /home/runner/work/urllib/urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +232 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 232, reused 230, downloaded 1, added 231 Progress: resolved 232, reused 230, downloaded 2, added 232, done ✗ Lockfile failed supply-chain policy check (297 entries in 2.1s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:08:38.909Z) 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 "sfw vp install" (cwd: /home/runner/work/urllib/urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +232 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 232, reused 230, downloaded 2, added 232, done ✗ Lockfile failed supply-chain policy check (297 entries in 1.7s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:08:42.678Z) 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 "sfw vp install" (cwd: /home/runner/work/urllib/urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +232 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 232, reused 230, downloaded 2, added 232, done ✗ Lockfile failed supply-chain policy check (297 entries in 1.7s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:08:42.373Z) 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 "sfw vp install" (cwd: /home/runner/work/urllib/urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +232 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 232, reused 230, downloaded 2, added 232, done ✗ Lockfile failed supply-chain policy check (297 entries in 1.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:08:43.184Z) 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 "sfw vp install" (cwd: /Users/runner/work/urllib/urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +233 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 233, reused 231, downloaded 0, added 231 Progress: resolved 233, reused 231, downloaded 2, added 233, done ✗ Lockfile failed supply-chain policy check (297 entries in 1.9s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:08:43.612Z) 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 "sfw vp install" (cwd: /Users/runner/work/urllib/urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +233 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 233, reused 231, downloaded 0, added 136 Progress: resolved 233, reused 231, downloaded 2, added 233, done ✗ Lockfile failed supply-chain policy check (297 entries in 2.5s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:08:48.599Z) 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 "sfw vp install" (cwd: /Users/runner/work/urllib/urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +233 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 233, reused 231, downloaded 0, added 54 Progress: resolved 233, reused 231, downloaded 0, added 211 Progress: resolved 233, reused 231, downloaded 2, added 233, done ✗ Lockfile failed supply-chain policy check (297 entries in 3.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:08:46.574Z) 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 "sfw vp install" (cwd: D:\a\urllib\urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +232 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 232, reused 230, downloaded 0, added 207 Progress: resolved 232, reused 230, downloaded 2, added 232, done ✗ Lockfile failed supply-chain policy check (297 entries in 3s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:09:12.512Z) 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 "sfw vp install" (cwd: D:\a\urllib\urllib) exited with code 1

? Verifying lockfile against supply-chain policies (297 entries)... Lockfile is up to date, resolution step is skipped Progress: resolved 1, reused 0, downloaded 0, added 0 Packages: +232 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Progress: resolved 232, reused 230, downloaded 0, added 217 Progress: resolved 232, reused 230, downloaded 2, added 232, done ✗ Lockfile failed supply-chain policy check (297 entries in 2.8s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@8.5.0 was published at 2026-06-15T15:50:40.000Z, within the minimumReleaseAge cutoff (2026-06-15T13:09:15.824Z) 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 "sfw vp install" (cwd: D:\a\urllib\urllib) exited with code 1