Release Readiness — .NET 11.0 preview 6 — 2026-07-20

Overall status: BLOCKED

❌ Nightly dogfood feed is STALE — 9 days (dotnet11 · 11.0.0-preview.6 (preview.6)). Latest build 11.0.0-preview.6.26360.8 published 2026-07-10. A fresh nightly is expected daily; builds appear to have stopped, so dogfooders can't validate recent fixes — check the nightly pipeline.

🔴 High-priority items — 1 item(s)

P/0 issues, P/0 PRs, dependency-flow PRs (darc + manual component bumps), and merge-up PRs in the main → net11.0 → release/11.0.1xx-preview6 daily-flow chain. Resolve these before treating the release as ready.

Release Captain Notes

The official/blessed preview build is embargoed from this public issue; an authorized maintainer confirms it locally via the release-readiness skill and reports it in the answer (see the branch-pins + inferred-subscription-health section below). Use this block for decisions/exceptions worth persisting — e.g. blessed ≠ branch pin, a rejected promotion, or a confirmed-broken subscription.

🏷️ Preview 6 component build — branch pins + inferred sub health

Run release readiness for release/11.0.1xx-preview6: report the blessed/official preview build (SDK + runtime) from the .NET Release Tracker, and verify the dotnet/android + dotnet/macios preview subscriptions are wired to the .NET 11.0.1xx SDK Preview 6 channel.

Flow-signal legend: 🔄 open dep-flow PR (flowing now) · ✅ merged ≤ 14 d · ⚠️ newest merge > 14 d (sub may have stalled) · ❌ no dep-flow PR into release/11.0.1xx-preview6 seen (sub may be missing — or the branch is brand new). Inferred from the public PR trail; confirm authoritative wiring locally with darc get-subscriptions --target-repo https://github.com/dotnet/maui --target-branch release/11.0.1xx-preview6. dotnet/dotnet (VMR) typically flows on manual trigger, so a quiet VMR is less alarming than a quiet android/macios.

Upstream legend: ✅ current = our pin is the tip of the component's release/11.0.1xx-preview6 branch · ⬆️ N ahead = that branch has N newer commit(s) than we bundle (FYI — may be post-preview churn or not-yet-blessed work; not necessarily a bump you need) · ⚠️ diverged = our pin isn't a clean ancestor of the branch tip (build tag / different line) — compare manually · — = couldn't determine (no same-named upstream branch, or the compare API was unavailable). Branch is derived from the survey ref, never hardcoded. dotnet/dotnet (VMR) advances constantly on manual trigger, so 'N ahead' there is expected churn and rarely actionable.

🧹 Cleanup follow-ups — 1 item(s)

Not release-blocking — these are post-ship housekeeping items to track separately.

Recent CI Failure Scanner signals (ci-scan)

Filtered to issues whose **Branch**: <name> body marker matches release/11.0.1xx-preview6 (auto-filed by the CI Failure Scanner workflow every 12h). Fresh issues (<24h) are flagged 🆕.

…and 34 more. Full list: open ci-scan issues.

Generated at 2026-07-20T12:18:02Z for dotnet/maui.

🕐 Report generated moments ago.

Tracker: net11-preview6 · mode=in-flight · branch=release/11.0.1xx-preview6 · survey=release/11.0.1xx-preview6

Target

Readiness checklist

Maestro / dependency-flow PRs

None found.

Release branch PRs

None found.

net11.0 inflight PRs

Showing 30 of 65 PRs.

Priority release blockers

None found.

Known Build Error watch list

Maintainer next actions

• Bug template versions: Add 11.0.0-preview.6 to the dropdown (PR against net11.0). Not release-blocking — this is post-release cleanup so users can file bugs against the right version.
• net11.0 preview-next bump: Confirm this is correct for the next preview train.
• net11.0 inflight branch health: Track as preview-next/inflight work; do not treat every inflight PR as a direct blocker for this release branch.
• Merge-up PRs (main → net11.0 → release/11.0.1xx-preview6): Resolve and merge each before shipping.
• Known Build Errors: Use [Epic] Improve CI Analysis Accuracy — Flaky Detection, KBE Integration, Auto-Triage #35052 CI truth to decide accepted-known vs release-blocking.
• CI Failure Scanner signals: Review recent ci-scan issues for ship-impact patterns.
• CI truth: Do not infer release readiness from GitHub checks alone; consume [Epic] Improve CI Analysis Accuracy — Flaky Detection, KBE Integration, Auto-Triage #35052 output when available.
• Xcode / ICM: Verify hosted Mac pool support and file/update ICM immediately when public Xcode availability requires it.
• Internal release pipelines: Release owner should inspect dnceng/internal pipeline details ASAP.

Public/internal data boundary

This public report intentionally omits internal logs, artifacts, private URLs, raw error text, secret names, account identifiers, and detailed dnceng/internal failure payloads. Use the local script with appropriate internal access for deeper validation.