Repository navigation
feat: support Angular 22 - #633
Merged
Merged
Conversation
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
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.
TL;DR
Updates Angular Hybrid and its example to Angular 22, keeping its release major aligned with
@uirouter/angularand making the package compile cleanly with TypeScript 6.Motivation
@uirouter/angularis now on major 22, while Angular Hybrid remains on 21. Aligning them keeps the framework packages in lockstep and gives the monorepo migration a coherent Angular 22 baseline.What
@uirouter/angular-hybridto22.0.0and narrow its Angular/UI-Router peers to the matching v22 lineValidation
yarn test/ package builddistwith the expected six files at version22.0.0test:downstreamdid not reach its projects locally because its ShellJS cache move crossed filesystems. The in-repository example was validated directly; the externalsample-app-angular-hybriddefault branch remains on Angular 21 and needs a coordinated Angular 22 update before that downstream lane can pass against this major.