GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — docs: describe AngularFire 21 as released, not as a release candidate (main) by armando-navarro · Pull Request #3814 · angular/angularfire

Conversation

@armando-navarro

@armando-navarro armando-navarro commented Oct 23, 2026

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

  • README.md and step 2 of docs/install-and-setup.md: install with ng add @angular/fire. The quickstart's "currently a release candidate" sentence is gone.
  • docs/install-and-setup.md and docs/install-firebase-tools.md: the "run ng add yourself, not through an AI agent" note is removed. It described the firebase-tools 15.26 crash from ng add @angular/fire stops with Cannot 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 on main since rc.2.
  • docs/version-21-upgrade.md: titled "Upgrading to AngularFire 21". The command is ng update @angular/core@21 @angular/cli@21 @angular/fire.
    • Only the first @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/fire needs no version there.
    • The Node.js note now says that updating AngularFire on its own needs ng update @angular/fire@21, not plain ng update @angular/fire.
    • The App Check note's qualifier becomes "(since 21.0.0-rc.2)", so readers coming from rc.0 or rc.1 still see that it changed between release candidates.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@armando-navarro
docs: describe AngularFire 21 as released, not as a release candidate
4a77ab3 
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 requested a review from tyler-reitz October 23, 2026 22:34
@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 approved these changes Oct 23, 2026
View reviewed changes

@tyler-reitz tyler-reitz left a comment

Copy link
Copy Markdown
Collaborator

There was a problem hiding this comment.

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.

Sorry, something went wrong.

Uh oh!

There was an error while loading. Please reload this page.
All reactions
@armando-navarro
armando-navarro merged commit 7146c2d into angular:main Oct 26, 2026
24 checks passed

Uh oh!

There was an error while loading. Please reload this page.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@tyler-reitz tyler-reitz tyler-reitz approved these changes

Uh oh!

There was an error while loading. Please reload this page.

Assignees

No one assigned

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

Milestone

22.0.0-rc.0

Development

Successfully merging this pull request may close these issues.

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

Uh oh!

There was an error while loading. Please reload this page.

2 participants

@armando-navarro @tyler-reitz
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.
You are visitor 01402503 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.