Repository navigation
docs: describe AngularFire 21 as released, not as a release candidate (main) - #3814
Open
armando-navarro wants to merge 1 commit into
Open
armando-navarro wants to merge 1 commit into
armando-navarro wants to merge 1 commit into
Conversation
Same change as angular#3813 on 21.0.x, carried to main because the public announcements and the rc.1 release notes link the upgrade guide at blob/main, so main's copy must read the same once 21.0.0 is on latest. The AI-agent note goes too: its fix (angular#3769) has been on main since rc.2. The upgrade command keeps @angular/fire unversioned: only the first @angular/ package in an ng update command picks the CLI that runs it. (cherry picked from commit ca70d4c)
armando-navarro
added
bump: patch
tyler-reitz
approved these changes
Oct 23, 2026
tyler-reitz
left a comment
tyler-reitz
left a comment
Collaborator
There was a problem hiding this comment.
Approving. One timing ask: please hold the merge until 21.0.0 is on latest. Right now latest is still 20.1.1, so once this lands, the README's ng add @angular/fire would install 20 on an Angular 21 app. This is the repo front page, so the gap shows up more here than on 21.0.x.
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.
Fixes #3812
The same change as #3813, which targets
21.0.x, applied tomain. The upgrade guide that the v21 announcements link isblob/main/docs/version-21-upgrade.md, somain's copy has to describe the release too. Four files change, the patch is identical to #3813's.Changes
README.mdand step 2 ofdocs/install-and-setup.md: install withng add @angular/fire. The quickstart's "currently a release candidate" sentence is gone.docs/install-and-setup.mdanddocs/install-firebase-tools.md: the "runng addyourself, not through an AI agent" note is removed. It described the firebase-tools 15.26 crash fromng add @angular/firestops withCannot read properties of undefined (reading 'email')when firebase-tools 15.26+ detects an AI agent #3768, and the fix (fix(schematics): read the signed-in Firebase account on firebase-tools 15.26+ #3769) has been onmainsince rc.2.docs/version-21-upgrade.md: titled "Upgrading to AngularFire 21". The command isng update @angular/core@21 @angular/cli@21 @angular/fire.@angular/package in the command picks the CLI that runs the update (docs: cover ng update stopping on a Node.js version message #3788), so@angular/fireneeds no version there.ng update @angular/fire@21, not plainng update @angular/fire.The README and quickstart on
mainstill describe an Angular 21 project. Their move to 22 is a separate change.Merge order
After #3813. This PR carries
Fixes #3812because GitHub only closes a linked issue when the pull request merges into the default branch, so #3813's ownFixesline does nothing.Verification
Documentation only. The staged patch matches #3813's commit
ca70d4cline for line (compared withdiffover both patches, ignoring blob ids). The samegit grepfor release-candidate wording leaves the two sections #3813 lists and the App Check qualifier, nothing else.