Repository navigation
docs: write the v22 upgrade guide for the release candidate - #3824
Merged
armando-navarro merged 3 commits intoOct 29, 2026
Merged
Conversation
The guide said @angular/fire@canary everywhere, which stops being the installable 22 build once 22.0.0-rc.0 publishes under next. Every command and sentence now says @next, and the title names the release candidate. Adds the two sections the guide was missing: the deploy builder deprecation from angular#3803, and other notes (Node.js 20 unsupported, TypeScript 6 config changes, the v21 migration re-running for release candidate users, how a canary install moves to the release candidate). Refs angular#3737
armando-navarro
added
type: chore
tyler-reitz
reviewed
Oct 29, 2026
tyler-reitz
left a comment
tyler-reitz
left a comment
Collaborator
There was a problem hiding this comment.
The canary note on line 77 needs another pass:
npm install @angular/fire@canarywrites a caret range (^22.0.1-canary...), not an exact version (ran it). From the CLI source,ng updatekeeps an existing^, so the guide's own command writes one too.canarynow publishes22.0.1-canary.*, built from the same commit as22.0.0-rc.0and ranked above it by semver.ng updateskips a target at or below the installed version (semver.lteinupdate/schematic/index.js), song update @angular/fire@nextshould be a no-op there (read from source, not run). It still moves the ten22.0.0-canary.*builds.
Scoping the note to 22.0.0-canary.*, or saying a 22.0.1 canary is already past the RC, would fix it. Everything else checked out against the source.
npm saves a canary as a ^ range, not an exact version. The canary tag now publishes 22.0.1-canary builds, which semver ranks above 22.0.0-rc.0, so ng update @angular/fire@next leaves them in place. 22.0.0-canary builds still move to the release candidate with @next. Refs angular#3737
Collaborator
Author
|
I've pushed a commit to address what you caught. Thanks Tyler. |
tyler-reitz
approved these changes
Oct 29, 2026
armando-navarro
removed
the
bump: patch
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.
Checklist
yarn install,yarn testrun successfully? Not run, no code changes. Markdown only, so the merge itself runs no CI. The next weekday scheduled run publishes a canary.Description
Prepares
docs/version-22-upgrade.mdfor22.0.0-rc.0, which publishes under thenexttag. Refs #3737.@angular/fire@canarybecomes@angular/fire@next, and the title names the release candidate instead of the canary.ng deployis deprecated in 22 and removed in 23. Hosting-only and Cloud Run deploys are not deprecated.^22.22.3 || ^24.15.0 || >=26.0.0), TypeScript 6 (stricton by default,downlevelIterationdropped,baseUrlandmoduleResolution: "node"deprecated), the v21 migration running once more for apps coming from a 21 release candidate, whichng updatecommand to run from each canary version, and screen tracking's move toreflectComponentTypeas a change with no effect on apps.Verification
ng update @angular/core@22 @angular/cli@22 @angular/fire@canaryon a fresh Angular 21.2.25 app with@angular/fire21.0.0: exit 0, Angular 22.2.3, TypeScript 6.0.3, both AngularFire migrations ran,ng buildpasses. The@nextcommand is the same command now that22.0.0-rc.0has published.grep canary docs/version-22-upgrade.mdfinds only the new note for canary installs.