Renovate has opened chore(deps): update dependency typescript to v7 on ten repositories. None of them can take it: every one is an Angular repository, and @angular/compiler-cli@22.1.4 declares
peerDependencies: { "typescript": ">=6.0 <6.1" }
so TypeScript 7 is outside the supported range. The install breaks the peer range and the compiler refuses to build against an unsupported version, which is a hard error rather than a warning. Angular has to ship support first.
The ten open PRs, all Angular, all pinned to ~6.0.0 or ^6.0.0:
| Repo |
PR |
| FerrFleet-Cloud |
#496 |
| FerrFlow-Cloud |
#648 |
| FerrGrowth-Cloud |
#504 |
| FerrLabs-Cloud |
#574 |
| FerrLens-Cloud |
#230 |
| FerrTrack-Cloud |
#619 |
| FerrVault-Cloud |
#487 |
| LFSX |
#136 |
| RoxyCloud |
#5 |
| UI |
#279 |
Each repo gets an allowedVersions rule in its own renovate.json rather than one rule here. The constraint is Angular's, not the org's: a repo without Angular should still take TypeScript 7 the day it is safe, and putting the rule in the shared preset would quietly hold back every future repo too. Ten small PRs, each carrying the reason next to the code it constrains, and each removable on its own the day that repo's Angular version supports 7.
Renovate closes the open PR by itself once the rule lands.
Removing this later: when Angular widens the peer range, drop the rule from the repos that have moved, one at a time. The description in each rule says what to check.
Renovate has opened
chore(deps): update dependency typescript to v7on ten repositories. None of them can take it: every one is an Angular repository, and@angular/compiler-cli@22.1.4declaresso TypeScript 7 is outside the supported range. The install breaks the peer range and the compiler refuses to build against an unsupported version, which is a hard error rather than a warning. Angular has to ship support first.
The ten open PRs, all Angular, all pinned to
~6.0.0or^6.0.0:Each repo gets an
allowedVersionsrule in its ownrenovate.jsonrather than one rule here. The constraint is Angular's, not the org's: a repo without Angular should still take TypeScript 7 the day it is safe, and putting the rule in the shared preset would quietly hold back every future repo too. Ten small PRs, each carrying the reason next to the code it constrains, and each removable on its own the day that repo's Angular version supports 7.Renovate closes the open PR by itself once the rule lands.
Removing this later: when Angular widens the peer range, drop the rule from the repos that have moved, one at a time. The description in each rule says what to check.