-
Notifications
You must be signed in to change notification settings - Fork 2.2k
Update Angular packages to version 19.2.0 and adjust version ranges #3639
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
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.
Checklist
yarn install,yarn testrun successfully? yesDescription
This PR updates the Angular dependency version ranges to support all Angular 19.x minor versions, not just 19.0.0. This resolves some dependency resolution issues where users with Angular 19.2.x projects encounter dependency conflicts when trying to use @angular/fire. To be clear, these issues were occurring on fresh Angular projects created via
ng new. See #3581 (comment) for more context.I've taken the liberty of aligning the Sample project with Angular 19.2.x dependency mappings, and tested to make sure that the sample project was building without issue.