pnpm-workspace.yamlminimumReleaseAgeExclude has accumulated ~30 version-pinned exclusions (pnpm 11.12, FullCalendar 7.0.1, the 2026-07-22 refresh, the Angular 22.0.6/22.0.8 patch train…). Each comment says "drop once older than the cutoff" — they all are now. Dead entries make it hard to see which exclusions are live.
Also minimumReleaseAgeStrict is false, so pnpm silently auto-adds exclusions for young direct deps during installs (that's how the Angular patch-train block appeared). Setting it true makes skipping the release-age gate an explicit, reviewed decision — a supply-chain improvement.
Acceptance criteria
remove every exclusion for a version older than the cutoff (and versions no longer in the lockfile)
decide minimumReleaseAgeStrict: true (recommended) and document the "how to bump a <24h release on purpose" step in the file comment
pnpm install --frozen-lockfile green in CI
Size: XS.
Filed from the 2026-10-02 spikersoft-angular pnpm outdated changelog review.
## Why
`pnpm-workspace.yaml` `minimumReleaseAgeExclude` has accumulated ~30 version-pinned exclusions (pnpm 11.12, FullCalendar 7.0.1, the 2026-07-22 refresh, the Angular 22.0.6/22.0.8 patch train…). Each comment says "drop once older than the cutoff" — they all are now. Dead entries make it hard to see which exclusions are live.
Also `minimumReleaseAgeStrict` is **false**, so pnpm silently *auto-adds* exclusions for young direct deps during installs (that's how the Angular patch-train block appeared). Setting it **true** makes skipping the release-age gate an explicit, reviewed decision — a supply-chain improvement.
## Acceptance criteria
- [ ] remove every exclusion for a version older than the cutoff (and versions no longer in the lockfile)
- [ ] decide `minimumReleaseAgeStrict: true` (recommended) and document the "how to bump a <24h release on purpose" step in the file comment
- [ ] `pnpm install --frozen-lockfile` green in CI
Size: **XS**.
---
_Filed from the 2026-10-02 spikersoft-angular `pnpm outdated` changelog review._
minimumReleaseAgeExclude pruned from ~30 pins to 2 (isomorphic-git@1.42.6, v86@0.5.469, both published 2026-10-01 and kept because they were <24h old at merge time). They have now aged past the cutoff and can be dropped on the next touch of pnpm-workspace.yaml.
minimumReleaseAgeStrict: true is set; the file comment documents how to take a sub-24h release on purpose (exact name@version + dated comment, drop once aged).
pnpm install --frozen-lockfile has passed in the build and test-and-lint jobs on every master run since the merge (e.g. master 637f469e5 fully green on 2026-10-05).
Closing — delivered by spikersoft-angular PR #1418 (merged 2026-10-02, commit c42face20).
- `minimumReleaseAgeExclude` pruned from ~30 pins to 2 (`isomorphic-git@1.42.6`, `v86@0.5.469`, both published 2026-10-01 and kept because they were <24h old at merge time). They have now aged past the cutoff and can be dropped on the next touch of `pnpm-workspace.yaml`.
- `minimumReleaseAgeStrict: true` is set; the file comment documents how to take a sub-24h release on purpose (exact `name@version` + dated comment, drop once aged).
- `pnpm install --frozen-lockfile` has passed in the build and test-and-lint jobs on every master run since the merge (e.g. master 637f469e5 fully green on 2026-10-05).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Why
pnpm-workspace.yamlminimumReleaseAgeExcludehas accumulated ~30 version-pinned exclusions (pnpm 11.12, FullCalendar 7.0.1, the 2026-07-22 refresh, the Angular 22.0.6/22.0.8 patch train…). Each comment says "drop once older than the cutoff" — they all are now. Dead entries make it hard to see which exclusions are live.Also
minimumReleaseAgeStrictis false, so pnpm silently auto-adds exclusions for young direct deps during installs (that's how the Angular patch-train block appeared). Setting it true makes skipping the release-age gate an explicit, reviewed decision — a supply-chain improvement.Acceptance criteria
minimumReleaseAgeStrict: true(recommended) and document the "how to bump a <24h release on purpose" step in the file commentpnpm install --frozen-lockfilegreen in CISize: XS.
Filed from the 2026-10-02 spikersoft-angular
pnpm outdatedchangelog review.Closing — delivered by spikersoft-angular PR #1418 (merged 2026-10-02, commit c42face20).
minimumReleaseAgeExcludepruned from ~30 pins to 2 (isomorphic-git@1.42.6,v86@0.5.469, both published 2026-10-01 and kept because they were <24h old at merge time). They have now aged past the cutoff and can be dropped on the next touch ofpnpm-workspace.yaml.minimumReleaseAgeStrict: trueis set; the file comment documents how to take a sub-24h release on purpose (exactname@version+ dated comment, drop once aged).pnpm install --frozen-lockfilehas passed in the build and test-and-lint jobs on every master run since the merge (e.g. master 637f469e5 fully green on 2026-10-05).