.NET 11 ships as .NET 8 reaches end of life
.NET 11 lands November 10 as a two-year STS release with runtime-native async and a higher hardware floor, the same day .NET 8's long-term support ends.
.NET 11 shipped November 10 as a standard-term-support release with two years of support, running to November 2028, and it landed on the same date that .NET 8's long-term support ran out. For a lot of teams the calendar made the upgrade decision.

Standard-term support means two years, not the three an LTS carries, and the label hides a detail. .NET 10, the current LTS, shipped in November 2025, so per the same policy page its three years and .NET 11's two end on the same day: November 14, 2028. The next long-term line is .NET 12 in November 2027. A shop leaving .NET 8 can take 10 for the LTS badge or 11 for the runtime work, and the support calendar does not distinguish between them. No release offers both the new features and a full three-year window, which is the point of alternating the two.
The headline runtime change is async without the compiler-generated state machine. Runtime-native async moves that machinery into the runtime itself, producing cleaner stack traces and lower overhead on the async paths that dominate server code, and C# 15 ships alongside it. Application code opts in with a project-level feature flag in this release; the runtime libraries are already compiled with it. Two other changes surface in build logs before anyone opens the release notes: Android builds move off Mono onto CoreCLR, and the minimum hardware baseline rises across x86, x64 and Arm64, dropping older instruction sets to cut maintenance.
The migration itself is the calmest part of the story, which is the reward for a runtime that takes compatibility seriously. Most .NET 8 services recompile against 11 with a target-framework bump and a dependency update, and the breaking changes that exist are documented and narrow. The work that bites is rarely the code. It is the estate: the build agents pinned to an old SDK, the container base images that need rebasing, and the one service whose owner left, whose pipeline nobody has run since 2024, and which is now the reason a routine upgrade needs a meeting.
The builder's read: plan around the support date, not the feature list. A service still on .NET 8 has been running unsupported bytes since November 10, so its migration is now forced rather than chosen. .NET 10 and .NET 11 are both valid landings and both expire in November 2028, so choose on features and dependency support, not on the label. The three-year window does not reopen until .NET 12 next November. Budget for the raised hardware floor regardless, because a runtime that drops old instruction sets can turn a green build into a runtime fault on the one legacy box nobody re-provisioned.