[Tracking] Move to .NET 11

Aperta
  • Qualcosa non va?
#372 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
csharp, docker, openapi
Ambito
backend-api-design, devops

Direzione di ricerca

This is a tracking issue, not a groomed story, and work is blocked until Microsoft.AspNetCore.OpenApi 11.0.0 is stable. When unblocked, start by grooming the framework step for TaskFlow.Api and TaskFlow.Api.Tests, then check the workflows, API Dockerfile, and the OpenAPI generation command (npm run gen:api). Done means the framework, CI/Docker, generated client and spec, migrations, and real-SQLite tests have been checked as described.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

blocked dependencies

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

  • #301 — Upgrade Microsoft.OpenApi to 3.x (3.5.4 or later) and remove the Dependabot ignore and the pin comment
  • #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 #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, #165 can go before or with #301. If not, #165 stays held and #301 cannot use an Asp.Versioning.OpenApi 10.x.
  3. Framework step, then #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.
  • #284 (TypeScript 7) is independent of this move and is gated on a typescript-eslint release, not on .NET.
Lingua principale
C#
Stelle
1
Fork
0
Merge medio
2h 2m
PR unite (30g)
98

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nevridge/TaskFlow

Tutte le issue di nevridge/TaskFlow

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.