Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Cerrado
  • ¿Algo no está bien?
#3,812 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

Ya se ha fusionado un pull request relacionado.

  • #3814 de @armando-navarro — fusionado

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
35/100
Tipo de issue
Documentación
Claridad
Bien especificado
Estado de actividad
Estancado
Stack tecnológico
angular, typescript
Área
documentation

Línea de trabajo

Read README.md, docs/install-and-setup.md, docs/version-21-upgrade.md, the quickstart, and docs/install-firebase-tools.md on the 21.0.x branch. Update the release-candidate wording and install/update examples to describe the 21.0.0 release, and remove the AI-agent note where the issue identifies it. Keep the specified App Check section and auth note unchanged; done when the branch docs consistently describe the release before tagging.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

comp: docs type: chore version: current (v17+)

With 21.0.0 about to be tagged from 21.0.x, the docs on that branch still describe the release candidate:

  • README.md and step 2 of docs/install-and-setup.md install with ng add @angular/fire@next, and the quickstart says AngularFire 21 "is currently a release candidate".
  • docs/version-21-upgrade.md is titled "Upgrading to the AngularFire 21 Release Candidate", its command ends in @angular/fire@next, and its Node.js note gives ng update @angular/[email protected] as the example.
  • The quickstart and docs/install-firebase-tools.md still carry the "run ng add yourself, not through an AI agent" note added for #3768. The fix (#3769) is on 21.0.x, so every 21.0.0 install has it.

Once 21.0.0 is on npm latest, the plain ng add @angular/fire and ng update commands install it, and the 21.0.0 tag would carry the release-candidate wording permanently. The branch's docs should describe the release before it is tagged.

Scope: documentation on 21.0.x only. The "21.0.0-rc.1 and earlier" section of docs/app-check.md stays, since it is a how-to for those releases. The note in docs/auth.md about importing beforeAuthStateChanged from firebase/auth is a separate change, because switching the sample back to @angular/fire/auth needs the #3770 fix verified in an app first.

Lenguaje dominante
TypeScript
Estrellas
7.8k
Forks
2.2k
Merge medio
2 d 7 h
PR fusionados (30 d)
18

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de angular/angularfire

Todos los issues de angular/angularfire

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.