API diff between .NET 11 Preview 6 and .NET 11 Preview 7

[github-actions]

Note

Incremental public API diff .NET 11 Preview 6 → .NET 11 Preview 7.

Incremental diff: 11.0-preview.6 (11.0.0-preview.6.26359.118) → 11.0-preview.7 (11.0.0-preview.7.26377.110). Track: incremental.

How this was generated

Generated by the api-diff skill / RunApiDiff.ps1.

• Previous: 11.0.0-preview.6.26359.118 @ https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json
• Current: 11.0.0-preview.7.26377.110 @ https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet11/nuget/v3/index.json
• Generated at: 2026-07-28T13:59:36Z
• Report count: 38 files

Status

Ready for review with Preview 7 locked down in terms of API shape.

Review checklist

Repo area owners

• ASP.NET - @dotnet/aspnet-api-review
• WinForms - @dotnet/dotnet-winforms
• WPF - @dotnet/wpf-developers @dotnet/dotnet-wpf-maintainers (no changes)
• Runtime - @JulieLeeMSFT @steveisok @agocke @lewing
• Libraries - @jeffhandley @SamMonoRT @karelz

Libraries area owners

• Extensions-Caching @dotnet/area-extensions-caching
• Extensions-DependencyInjection @dotnet/area-extensions-dependencyinjection
• Extensions-Primitives @dotnet/area-extensions-primitives
• System.Diagnostics.Process @dotnet/area-system-diagnostics-process
• System.IO.Compression @dotnet/area-system-io-compression
• System.Memory @dotnet/area-system-memory
• System.Net (Http, NameResolution) @dotnet/ncl
• System.Runtime @dotnet/area-system-runtime
• System.Runtime.InteropServices @dotnet/interop-contrib
• System.Runtime.Intrinsics @dotnet/area-system-runtime-intrinsics
• AssemblyLoader (System.Runtime.Loader) @agocke @elinor-fung
• System.Numerics (System.Runtime.Numerics) @dotnet/area-system-numerics
• System.Security (Cryptography) @bartonjs @vcsjones @dotnet/area-system-security
• System.Text.Json @dotnet/area-system-text-json

Feedback applied

Temporary attribute exclusions (this diff only):

• T:System.Diagnostics.CodeAnalysis.UnconditionalSuppressMessageAttribute — excluded per reviewer request to suppress attribute property typo corrections from the diff (Microsoft.Extensions.Identity.Stores). The change in that file was a Justification string typo fix ("annoated" → "annotated"), not a real API change.

Permanent exclusions added this run: None.

Automation state

# api-diff:state:begin
# api-diff-marker: 11.0-preview.6_to_11.0-preview.7
track: "incremental"
previous-version-milestone: "11.0-preview.6"
current-version-milestone: "11.0-preview.7"
previous-version: "11.0.0-preview.6.26359.118"
current-version: "11.0.0-preview.7.26377.110"
previous-feed: "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet-public/nuget/v3/index.json"
current-feed: "https://pkgs.dev.azure.com/dnceng/public/_packaging/dotnet11/nuget/v3/index.json"
status: "in-development"
report-count: 38
generated-at: "2026-07-28T13:59:36Z"
temporary-attributes-excluded: ["T:System.Diagnostics.CodeAnalysis.UnconditionalSuppressMessageAttribute"]
# api-diff:state:end

Generated by API Diff Worker · 81.9 AIC · ⌖ 5.43 AIC · ⊞ 11.2K · ◷

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

[svick]

@jeffhandley The old workflow was to notify code owners with changes and ask them to check that the changes are correct. How is that going to work with this version?

[jeffhandley]

Previously, the worker created API-diff PRs as drafts and marked them Ready for Review only after the diff reached code-complete (when development had moved to the next major). It did not generate a review checklist or explicitly request the product and library-area owners; any reviewer requests followed the repository's normal CODEOWNERS behavior.

The new workflow changes retain that draft-to-ready transition and add a review checklist before the feedback section. It lists the repo owners and derives affected library-area owners from the live dotnet/runtime area-owners.md mapping. Existing open API-diff PRs will receive the revised body on their next daily run.

[svick]

@jeffhandley It looks like the agent got confused about how to use safeoutputs and so the PR description was not updated:

Warning: ⚠️ report_incomplete: update_pull_request limit exhausted before body refresh
Details: The first update_pull_request call was sent without the body (title-only), consuming the 1-per-run limit. The second call with the full body (including the new generated_at watermark 2026-07-23T13:56:37Z and review checklist) was rejected. The PR body still shows generated_at: 2026-07-22T13:56:21Z, so the watermark was not advanced. The next scheduled run will re-enter this metadata-only path.

Though if this is a rare problem and tomorrow's run is going to be fine, this might not be worth addressing.

[github-actions]

Commit pushed: 218d9c6

Generated by API Diff Worker · 49.2 AIC · ⌖ 5.9 AIC · ⊞ 11.2K

[github-actions]

Commit pushed: 5bd113c

Generated by API Diff Worker · 81.9 AIC · ⌖ 5.43 AIC · ⊞ 11.2K

[jeffhandley]

I verified this against the Preview 7 builds, and verified the agent removed the noisy attribute changes that only fixed typos in description text.