Closed
Move CSRF .NET 11 guidance into the 10-to-11 migration article#37343
Conversation
…rticle and TOC node
Copilot
AI
changed the title
[WIP] Add section for .NET 11 CSRF support in upgrade article
Move CSRF .NET 11 guidance into the 10-to-11 migration article
Jul 13, 2026
tdykstra
approved these changes
Jul 13, 2026
tdykstra
marked this pull request as ready for review
July 13, 2026 23:57
Contributor
|
Closing as duplicate of #37329 |
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.
The "Adopt automatic CSRF protection in .NET 11" article was a standalone TOC node, but per the version-update TOC convention, the "10 to 11" node should be the single source of truth for everything needed in that upgrade.
Changes
aspnetcore/migration/100-to-110.md— Added## Adopt automatic CSRF protectionsection containing the full content from the deleted article; heading levels shifted (H2→H3, H3→H4) to fit the new nesting contextaspnetcore/migration/antiforgery-to-csrf.md— Deletedaspnetcore/toc.yml— Removed the standalone CSRF TOC node; "Version updates" now follows "Overview" directly.openpublishing.redirection.json— Added redirect:aspnetcore/migration/antiforgery-to-csrf.md→/aspnet/core/migration/100-to-110aspnetcore/security/csrf-protection.md— Updated threexref:migration/antiforgery-to-csrfreferences →xref:migration/100-to-110aspnetcore/breaking-changes/11/blazor-server-side-rendering-deferred-cross-site-request-forgery-protection.md— Updated onexref:migration/antiforgery-to-csrfreference →xref:migration/100-to-110Internal previews