Skip to content

Upgrade to .NET 10 with multi-targeting net8.0;net10.0 - #85

Merged
enrico-barbieri-engagelabs merged 1 commit into
mainfrom
upgrade-net10
Sep 3, 2026
Merged

enrico-barbieri-engagelabs merged 1 commit into
mainfrom
upgrade-net10

Conversation

@enrico-barbieri-engagelabs

Copy link
Copy Markdown
Collaborator

Cosa cambia

  • EngageLabs.MinimalApi e ShowcaseApp ora multi-targettano net8.0 e net10.0: chi consuma il pacchetto da app ancora su .NET 8 continua a funzionare, chi è su .NET 10 ottiene l'asset dedicato.
  • Microsoft.AspNetCore.Authentication.JwtBearer pinnato per TFM (8.0.30 / 10.0.11), dato che quel pacchetto segue la versione della runtime.
  • NSwag.AspNetCore invariato a 14.7.1: ha già un gruppo di asset net10.0, nessuna diversificazione necessaria.
  • CI/CD (CI.yml, CD.yml): actions/setup-dotnet installa sia l'SDK 8.x che 10.x.

Verifiche locali

  • dotnet restore, dotnet format --verify-no-changes, dotnet build (entrambi i TFM), dotnet test, dotnet pack
  • .nupkg ispezionato: contiene sia lib/net8.0 che lib/net10.0

🤖 Generated with Claude Code

- EngageLabs.MinimalApi and ShowcaseApp now multi-target net8.0 and
  net10.0, so consumers still on .NET 8 keep working while .NET 10
  is supported.
- Microsoft.AspNetCore.Authentication.JwtBearer is pinned per TFM
  (8.0.30 / 10.0.11) since that package follows the runtime version.
  NSwag.AspNetCore is left unpinned as it already ships a net10.0
  asset group.
- CI/CD workflows install both .NET 8 and .NET 10 SDKs.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@enrico-barbieri-engagelabs
enrico-barbieri-engagelabs merged commit c918e3c into main Sep 3, 2026
4 checks passed
@enrico-barbieri-engagelabs
enrico-barbieri-engagelabs deleted the upgrade-net10 branch September 3, 2026 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant