[Tracking] Move to .NET 11 #372

Groups the work for moving TaskFlow from .NET 10 to .NET 11. This is a place to collect the pieces, not a groomed story. Blocked until Microsoft.AspNetCore.OpenApi 11.0.0 is stable (as of 2026-10-30 NuGet has 11.0.0-rc.3.26522.148 and no stable 11.0.0). When it ships, groom the framework step below before starting.

Sub-issues

• Upgrade Microsoft.OpenApi to 3.x when moving to .NET 11 #301 — Upgrade Microsoft.OpenApi to 3.x (3.5.4 or later) and remove the Dependabot ignore and the pin comment
• chore: upgrade Asp.Versioning.Mvc to v10.0.0 #165 — Upgrade Asp.Versioning.Mvc, .ApiExplorer and add Asp.Versioning.OpenApi. Held: Asp.Versioning.OpenApi 10.2.3 depends on Microsoft.OpenApi [2.7.5, 3.0.0), which blocks Upgrade Microsoft.OpenApi to 3.x when moving to .NET 11 #301 until Asp.Versioning ships a release that accepts Microsoft.OpenApi 3.x

Not yet issues (to groom when .NET 11 is stable)

• Framework step: TargetFramework and MicrosoftPlatformVersion in TaskFlow.Api and TaskFlow.Api.Tests, EF Core 11 and its provider packages, Microsoft.Extensions.* and OpenTelemetry package compatibility
• CI and Docker: .NET SDK version in the workflows, the API Dockerfile base images, and the Dependabot docker block
• Regenerate the OpenAPI spec and the web client (npm run gen:api) and check the output is unchanged or intentionally changed
• Check migrations still apply on startup and the real-SQLite tests still pass

Suggested order

1. Wait for stable Microsoft.AspNetCore.OpenApi 11.0.0.
2. Check whether an Asp.Versioning.* release supports Microsoft.OpenApi 3.x. If so, chore: upgrade Asp.Versioning.Mvc to v10.0.0 #165 can go before or with Upgrade Microsoft.OpenApi to 3.x when moving to .NET 11 #301. If not, chore: upgrade Asp.Versioning.Mvc to v10.0.0 #165 stays held and Upgrade Microsoft.OpenApi to 3.x when moving to .NET 11 #301 cannot use an Asp.Versioning.OpenApi 10.x.
3. Framework step, then Upgrade Microsoft.OpenApi to 3.x when moving to .NET 11 #301.

Notes

• Asp.Versioning.Mvc 10.2.1 targets net10.0 only (nuspec, checked 2026-10-30). Whether its net10.0 assets work on net11.0 is part of step 2.
• Upgrade to TypeScript 7 once typescript-eslint supports it #284 (TypeScript 7) is independent of this move and is gated on a typescript-eslint release, not on .NET.