Skip to content

Add net10.0 and net11.0 support - #14

Merged
johnkors merged 1 commit into
mainfrom
jk/net10-net11-support
Sep 21, 2026
Merged

johnkors merged 1 commit into
mainfrom
jk/net10-net11-support

Conversation

@johnkors

Copy link
Copy Markdown
Contributor
  • multi-target net8.0;net9.0;net10.0;net11.0 in CronBackgroundServices.csproj, keeping all existing TFMs
  • bump Microsoft.Extensions.Hosting.Abstractions / Logging.Abstractions floor from 9.0.0 to 10.0.0 (latest GA); 11.0.0 packages don't exist yet, RC only, so not referenced directly
  • net11.0 is RC-only today (SDK 11.0.100-rc.1, no GA Microsoft.Extensions.* 11.0.0 package) — lib/net11.0 in the nupkg is built against RC reference assemblies until .NET 11 GAs
  • CI/Release/PreRelease workflows now install the .NET 11 SDK via dotnet-quality: preview (one SDK builds all four TFMs; reference assemblies for the older TFMs come from NuGet regardless of installed SDK)
  • verified locally: dotnet build/test/pack clean (0 warnings, 0 errors) for net8.0/net9.0/net10.0/net11.0, plus the Samples/ConsoleApp project, and confirmed the packed nupkg contains all four lib/net* folders with net8.0 correctly resolving real net8.0 assets (not a netstandard2.0 fallback) from the bumped packages
  • the PreRelease.yml edit here will conflict with PR ci: use NuGet OIDC trusted publishing instead of a long-lived API key #13's Release/PreRelease consolidation — flagging for awareness, did not touch anything OIDC/trusted-publishing related

add .NET 10 and .NET 11 target frameworks
bump Microsoft.Extensions.*.Abstractions floor to 10.0.0
install preview-quality .NET 11 SDK in CI/Release/PreRelease

+semver:minor
@johnkors
johnkors force-pushed the jk/net10-net11-support branch from 9ff10df to bca4ffc Compare September 21, 2026 16:42
@johnkors
johnkors merged commit 65d9d29 into main Sep 21, 2026
2 checks passed
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