Skip to content

docs: note the removed @angular/platform-server peer in the v21 upgrade guide - #3795

Merged
armando-navarro merged 5 commits into
angular:mainfrom
armando-navarro:a67-upgrade-guide-note
Oct 10, 2026
Merged

armando-navarro merged 5 commits into
angular:mainfrom
armando-navarro:a67-upgrade-guide-note

Conversation

@armando-navarro

@armando-navarro armando-navarro commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

Refs #3667

Adds the removal of the optional @angular/platform-server peer (#3792) to the "Other notes" list in docs/version-21-upgrade.md, next to the existing note about @angular/platform-browser-dynamic.

…de guide

The upgrade guide's "Other notes" already lists the removed
@angular/platform-browser-dynamic peer. The optional
@angular/platform-server peer is gone too, and apps need no change.
@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 8, 2026
@armando-navarro armando-navarro added this to the 21.0.0-rc.2 milestone Oct 8, 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.

Content looks right, so I am holding the approval rather than giving it, since approval is the only gate here and it would make this mergeable ahead of rc.2. Ping me when rc.2 is ready and I will approve it then.

Two small things while it waits.

The sentence says "peer dependency" twice. Reads better collapsed:

The obsolete @angular/platform-browser-dynamic and the unused optional @angular/platform-server peer dependencies were removed. No action is needed.

And @angular/platform-browser-dynamic is already gone from published 20.1.0, so for anyone upgrading from latest that half of the bullet describes something their current version already did. Worth either saying which removal landed when, or leaving it, since "No action is needed" covers both either way. Your call, it is the sentence this PR happens to touch rather than anything it introduces.

The line said "peer dependency" twice. Naming both packages before one "peer dependencies" reads better.
@armando-navarro

Copy link
Copy Markdown
Collaborator Author

@tyler-reitz This is a draft PR, so an approval doesn't make it mergeable until I pull it out of draft state. If it looks good, could you approve it like you did a previous draft PR I wanted held for a release? It stays a draft until 21.0.0-rc.2 is ready to release, which is very soon.

I took your first suggestion, so the line names "peer dependencies" once. I'm leaving the second as it is, since "No action is needed" holds for readers coming from either 20.0.x or 20.1.0.

@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 while it is still a draft, per the rc.2 hold in the description. The combined note reads correctly coming from either 20.0.x or 20.1.0.

The example named 21.0.0-rc.1, which would install the older release
candidate once 21.0.0-rc.2 is out.
…uide

21.0.0-rc.2 skips App Check during server rendering (angular#3773). The guide
now says so and links the App Check page's server-rendering section.
@armando-navarro
armando-navarro marked this pull request as ready for review October 10, 2026 04:52
@armando-navarro
armando-navarro merged commit e11f0da into angular:main Oct 10, 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.

2 participants