Skip to content

docs: describe AngularFire 21 as released, not as a release candidate (main) - #3814

Merged
armando-navarro merged 1 commit into
angular:mainfrom
armando-navarro:b40-docs-21-released-main
Oct 26, 2026
Merged

armando-navarro merged 1 commit into
angular:mainfrom
armando-navarro:b40-docs-21-released-main

Conversation

@armando-navarro

Copy link
Copy Markdown
Collaborator

Fixes #3812

The same change as #3813, which targets 21.0.x, applied to main. The upgrade guide that the v21 announcements link is blob/main/docs/version-21-upgrade.md, so main's copy has to describe the release too. Four files change, the patch is identical to #3813's.

Changes

The README and quickstart on main still describe an Angular 21 project. Their move to 22 is a separate change.

Merge order

After #3813. This PR carries Fixes #3812 because GitHub only closes a linked issue when the pull request merges into the default branch, so #3813's own Fixes line does nothing.

Verification

Documentation only. The staged patch matches #3813's commit ca70d4c line for line (compared with diff over both patches, ignoring blob ids). The same git grep for release-candidate wording leaves the two sections #3813 lists and the App Check qualifier, nothing else.

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 armando-navarro added bump: patch Size of the change: a fix or docs change that reaches users comp: docs Documentation. type: chore Maintenance with no user-facing behavior change. labels Oct 23, 2026
@armando-navarro armando-navarro added this to the 22.0.0-rc.0 milestone Oct 23, 2026

@tyler-reitz tyler-reitz left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

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.

@armando-navarro
armando-navarro merged commit 7146c2d into angular:main Oct 26, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bump: patch Size of the change: a fix or docs change that reaches users comp: docs Documentation. type: chore Maintenance with no user-facing behavior change.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

The docs on 21.0.x still describe AngularFire 21 as a release candidate

2 participants