Context
Commit 83840fd dropped the @types/node@22.19.20 entry from minimumReleaseAgeExclude in pnpm-workspace.yaml. It was auto-added during the pnpm 11 migration (#5) because the package was <24h old.
It was pushed before the package aged out of pnpm 11's 1-day minimumReleaseAge gate, so main CI (and local pnpm install) will fail the supply-chain policy check on this one package until it ages out.
- Published: 2026-06-05T22:33:36Z
- Ages out (gate clears): 2026-06-06T22:33:36Z
- Failure (expected/benign):
[ERR_PNPM_MINIMUM_RELEASE_AGE_VIOLATION] 1 lockfile entries failed verification:
@types/node@22.19.20 ... within the minimumReleaseAge cutoff
The lockfile is unchanged — this is purely the policy gate, not a real dependency problem.
Action
After 2026-06-06T22:33:36Z, re-run the main CI (re-run the failed jobs on the latest run, or push an empty commit). It should go green with no code changes.
Close when
main CI is green post-22:33 UTC. No fix needed — self-resolving.
Context
Commit 83840fd dropped the
@types/node@22.19.20entry fromminimumReleaseAgeExcludeinpnpm-workspace.yaml. It was auto-added during the pnpm 11 migration (#5) because the package was <24h old.It was pushed before the package aged out of pnpm 11's 1-day
minimumReleaseAgegate, somainCI (and localpnpm install) will fail the supply-chain policy check on this one package until it ages out.The lockfile is unchanged — this is purely the policy gate, not a real dependency problem.
Action
After 2026-06-06T22:33:36Z, re-run the
mainCI (re-run the failed jobs on the latest run, or push an empty commit). It should go green with no code changes.Close when
mainCI is green post-22:33 UTC. No fix needed — self-resolving.