Skip to content

Add .NET 11 Preview 3 release notes draft#10344

Open
richlander wants to merge 4 commits intomainfrom
release-notes/11.0-preview3
Open

Add .NET 11 Preview 3 release notes draft#10344
richlander wants to merge 4 commits intomainfrom
release-notes/11.0-preview3

Conversation

@richlander
Copy link
Copy Markdown
Member

Summary

  • add the initial .NET 11 Preview 3 release notes draft
  • include freshly regenerated changes.json and build-metadata.json
  • use a clean rerun branch for review without the prior PR history

This PR is the fresh manual rerun while the agentic workflow authentication issue is still being debugged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- [Unsafe Evolution remains a preview feature in .NET 11](#unsafe-evolution-remains-a-preview-feature-in-net-11)
- [Breaking changes](#breaking-changes)

## Unsafe Evolution remains a preview feature in .NET 11
Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This title states the obvious. We could re-use it every time and it would still be true.

How about "Unsafe Evolution project adds clearer warnings and errors"?

Also, is the new() constraint specific to Unsafe Evolution?

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. I agree the heading is too generic as written. I'll tighten it to focus on the actual Preview 3 additions, likely along the lines of your suggestion, and I'll re-check whether the new() constraint item is specific enough to keep under the Unsafe Evolution framing.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Acted on. I updated the heading to focus on the actual Preview 3 additions, and yes — the new() constraint item is coming from dotnet/roslyn #82647, which is explicitly part of the Unsafe Evolution work.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
@richlander richlander marked this pull request as ready for review April 7, 2026 22:43
Co-authored-by: Daniel Roth <daroth@microsoft.com>
@danroth27
Copy link
Copy Markdown
Member

@guardrex

Copy link
Copy Markdown
Member

@jeffhandley jeffhandley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Signing off on Libraries

Copy link
Copy Markdown
Member

@ilonatommy ilonatommy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One remark for variable height feature. Virtualization and Web Worker template bug fixes checked and approved.


Thank you [@manandre](https://github.com/manandre) for this contribution!

## Virtualize adapts to variable-height items at runtime
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There was one meaningful change that this feature introduced: bumped OverscanCount default value from 3 to 15 to increase precision of average item height calculations. Both the fact of change and the reason is important.

* Add F# release notes for .NET 11 Preview 3
@mikekistler
Copy link
Copy Markdown
Contributor

Did Support HTTP Query #65714 make it into preview3? If so it seems to be missing from aspnetcore.md.

- Preview 3 updates `Microsoft.Data.SqlClient` to 7.0.0. Review the SqlClient
release notes if you depend on provider-specific SQL Server behavior
([dotnet/efcore #37949](https://github.com/dotnet/efcore/pull/37949)).

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants