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

? Verifying lockfile against supply-chain policies (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 1.7s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:32:42.382Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 2.9s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:32:44.199Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 1.7s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:32:47.611Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 2.6s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:32:48.226Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 2.7s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:33:08.819Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 1.9s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:33:15.756Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 2s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:33:29.897Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 1.3s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:33:34.113Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 1.8s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:33:38.966Z) 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 (296 entries)... ✗ Lockfile failed supply-chain policy check (296 entries in 1.9s) [ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification: undici@7.27.0 was published at 2026-06-01T12:16:04.000Z, within the minimumReleaseAge cutoff (2026-06-01T03:33:41.596Z) 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.

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-latest requests are being redirected to windows-2025-vs2026 by June 15, 2026