Align devkit tooling with Angular 22; group dependabot's angular updates - #5792
Merged
norman-abramovitz merged 2 commits intoAug 9, 2026
Merged
Conversation
Bump the devkit's @Angular-devkit packages 21.2.19 to 22.1.3 in lockstep (architect 0.2102.19 to 0.2201.3) and TypeScript 5.9.2 to 6.0.3, the root toolchain's major. The devkit was left behind by the Angular 22 upgrade; dependabot proposed the same bumps one package at a time, which cannot build — the @Angular-devkit set only works in matching versions (mixed sets fail with nested-type TS2742 errors in the devkit build). Supersedes cloudfoundry#5780, cloudfoundry#5781, cloudfoundry#5788, cloudfoundry#5789 and the TypeScript-7 proposal in cloudfoundry#5785.
The Angular packages only work in lockstep, so per-package PRs arrive mutually incompatible; group them per ecosystem. TypeScript majors are pinned by Angular's supported range and move with framework upgrades, not on their own — ignore them in both ecosystems.
This was referenced Aug 9, 2026
chore(deps): bump @angular-devkit/core from 21.2.19 to 22.1.3 in /src/frontend/packages/devkit
#5781
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The first dependabot sweep from the #5779 config surfaced real debt in unusable slices: the devkit package was left on
@angular-devkit21.2.19 / TypeScript 5.9.2 by the Angular 22 upgrade, and dependabot proposed the catch-up one package at a time. The@angular-devkitset only works in matching versions — each single-package PR produces a mixed set that fails the devkit build with nested-type TS2742 errors (#5781, #5788, #5789 fail exactly this way).Two commits:
@angular-devkitpackages to 22.1.3 in lockstep (architect 0.2201.3) and TypeScript to 6.0.3 — the root toolchain's major, rather than the 7.0.2 dependabot proposed. The devkit installs and builds in isolation (build/ensure-devkit.cjsruns its ownnpm install+tsc), so this was verified by running that exact sequence locally, plus the full gate.@angular*/@schematics/*per ecosystem so lockstep packages arrive as one PR, and ignore TypeScript majors in both ecosystems — those move with framework upgrades, not on their own.Supersedes #5780, #5781, #5785, #5788, #5789 (will be closed with
@dependabot ignorecomments). The remaining five root-ecosystem PRs (#5782, #5783, #5784, #5786, #5787) are independently green — the bun ecosystem maintainsbun.locknatively — and can merge as-is.