Skip to content

chore(deps): align @angular-devkit packages to 21.2.19 in devkit - #5628

Merged
norman-abramovitz merged 1 commit into
cloudfoundry:developfrom
nabramovitz:devkit-align-devkit-21219
Jul 11, 2026
Merged

norman-abramovitz merged 1 commit into
cloudfoundry:developfrom
nabramovitz:devkit-align-devkit-21219

Conversation

@nabramovitz

Copy link
Copy Markdown
Contributor

Aligns the @angular-devkit/* packages in devkit to 21.2.19.

Supersedes the Dependabot PR #5626, which bumped only
@angular-devkit/build-angular to 21.2.19 and left core, schematics
and architect at 21.2.14. With that skew, build-angular resolved a
nested @angular-devkit/core copy and devkit's tsc build failed on
incompatible Logger types between the two copies — the preinstall
step exited 1, so every CI job went red.

Bumping all four together fixes the build. Verified locally:
bun run build-devkit succeeds, the override block from #5624 is
preserved, and npm audit is unchanged (the build-angular esbuild path
advances to 0.28.1; the remaining low/moderate advisories are the same
vite-path esbuild and sockjs-path uuid as before).

Dependabot bumped @angular-devkit/build-angular to 21.2.19 but left
@angular-devkit/core, /schematics and /architect at 21.2.14. build-angular
then resolved a nested @angular-devkit/core copy, and devkit's tsc build
failed on incompatible Logger types between the two copies — the
preinstall step exited 1, so every CI job went red.

Align all @angular-devkit/* to 21.2.19. devkit builds again; the override
block is preserved and the build-angular esbuild path advances to 0.28.1.

@norman-abramovitz norman-abramovitz left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@norman-abramovitz
norman-abramovitz merged commit 8963f51 into cloudfoundry:develop Jul 11, 2026
21 checks passed
@nabramovitz
nabramovitz deleted the devkit-align-devkit-21219 branch July 11, 2026 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants