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 by armando-navarro · Pull Request #3813 · angular/angularfire

Conversation

@armando-navarro

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

Copy link
Copy Markdown
Collaborator

Fixes #3812

Prepares the docs on 21.0.x for the 21.0.0 tag. Four files change.

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) is on this branch.
  • 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.

Left as they are: the "AngularFire 21.0.0-rc.1 and earlier" section of docs/app-check.md, which is a how-to for those releases, and the docs/auth.md note on importing beforeAuthStateChanged from firebase/auth, which is a separate change.

Merge order

Merge before 21.0.0 is tagged, so the tag carries these docs. Between the merge and the tag, the plain ng add @angular/fire in these docs does not install 21 on an Angular 21 app, since latest is 20.1.1 until the tag publishes.

Verification

Documentation only. git grep -i -E "@next|release candidate|-rc\.[0-9]" over docs/ and README.md on the branch returns the two sections listed above as left in place and the App Check note's "(since 21.0.0-rc.2)" qualifier, nothing else. The install and update commands cannot be run against 21.0.0 until it is on latest.

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
ca70d4c
The docs on 21.0.x still install with @angular/fire@next, call 21 a
release candidate, and carry the AI-agent note for the firebase-tools
15.26 crash that angular#3769 fixed on this branch. The 21.0.0 tag is cut from
this branch, so its docs should describe the release.

The upgrade command keeps @angular/fire unversioned: only the first
@angular/ package in an ng update command picks the CLI that runs it.
The Node.js note gives the versioned form for updating AngularFire alone.
@armando-navarro
armando-navarro requested a review from tyler-reitz October 23, 2026 22:19
@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 21.0.0 milestone Oct 23, 2026
tyler-reitz
tyler-reitz approved these changes Oct 23, 2026
View reviewed changes
@armando-navarro armando-navarro mentioned this pull request Oct 23, 2026
docs: describe AngularFire 21 as released, not as a release candidate (main) #3814
Merged
@armando-navarro
armando-navarro merged commit 2f5ef49 into angular:21.0.x Oct 26, 2026
18 checks passed

Uh oh!

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

armando-navarro added a commit that referenced this pull request Oct 26, 2026
@armando-navarro
docs: describe AngularFire 21 as released, not as a release candidate (…
7146c2d
…#3814)

Same change as #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 (#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)
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

21.0.0

Development

Successfully merging this pull request may close these issues.

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.