What's New Automation

[wadepickett]

Description

Automation prompt for Copilot for creating draft What's New PR from Release Notes output:

Task: Create Include Files for ASP.NET Core .NET 11 Preview 2 Release Notes

Context

The dotnet/core repository contains per-preview release notes, such as:
release-notes/11.0/preview/preview2/aspnetcore.md

The dotnet/AspNetCore.Docs repository contains a cumulative "What's New in ASP.NET Core in .NET 11" article at:
AspNetCore.Docs/aspnetcore/release-notes/aspnetcore-11.md`

This What's New article is organized by product area (e.g., "Authentication and authorization", "Performance", etc.) and uses Markdown include directives to pull in individual feature descriptions from:
aspnetcore/release-notes/aspnetcore-11/includes/<feature-name>.md

Each include file describes a single feature or change. For example:

[!INCLUDE[](~/release-notes/aspnetcore-11/includes/identity-time-provider.md)]

Source

The Preview 2 ASP.NET Core release notes from dotnet/core at branch dotnet11-preview2:
release-notes/11.0/preview/preview2/aspnetcore.md

Instructions

All changes introduced in this PR are only to be on the AspNetCore.Doc repo.

1. Create new include files in dotnet/AspNetCore.Docs at:
   AspNetCore.Docs/aspnetcore/release-notes/aspnetcore-11/includes/

2. Naming convention: Follow the existing naming pattern (lowercase, hyphenated, descriptive) and append -p2 to each filename to indicate it originated from Preview 2. Example:
   native-otel-tracing-p2.md

3. One include file per feature/section, except performance improvements which should be combined into a single performance-improvements-p2.md file.

4. Exclusions:

   • Blazor: Do not create include files for any Blazor-related features or changes (e.g., "TempData support for Blazor"). Those will be handled separately later.
   • Bug fixes: Do not create include files for the bug fixes section.
   • Community contributors list: Do not create a standalone include file for the community contributors section.

5. Preserve community contributor thank-yous: If a feature or improvement section in the release notes thanks a community contributor inline (e.g., "Thank you @baywet for this contribution!"), keep that acknowledgment in the corresponding include file.

6. Preserve breaking change designations: If a section is marked as a "Breaking Change" (e.g., OpenAPI 3.2.0), preserve that designation in the include file content.

7. Remove preview-specific references: Do not include references to the specific preview number (e.g., "Preview 2") in the include file content. The What's New article is presented as a cumulative announcement of what's new in ASP.NET Core in .NET 11 as a whole, not tied to individual previews.

8. Content adaptation: Adapt the release note content for the include file format — these are meant to be embedded in a larger article, so they should read as self-contained sections (use ### headings, not ## or #). Follow the style and tone of existing include files in the repository.

9. Update aspnetcore-11.md: Add [!INCLUDE[](~/release-notes/aspnetcore-11/includes/<filename>.md)] directives for each new include file in the appropriate product area section of the What's New article. Place new includes after any existing includes within each section, following the established format.

Page URL

https://learn.microsoft.com/en-us/aspnet/core/release-notes/aspnetcore-11?view=aspnetcore-10.0&tabs=minimal-apis

Content source URL

https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/release-notes/aspnetcore-11.md

Document ID

5f749050-bd63-c782-f5a6-834dbaa7a1bc

Platform Id

e8eaff50-8e78-f831-b4d1-c5309fcb547e

Article author

@wadepickett

Metadata

• ID: 5f749050-bd63-c782-f5a6-834dbaa7a1bc
• PlatformId: e8eaff50-8e78-f831-b4d1-c5309fcb547e
• Service: aspnet-core
• Sub-service: release-notes

Related Issues