Skip to content

Mark the NuGet package as .NET 10 instead of .NET 8 - #6

Merged
kblok merged 1 commit into
mainfrom
cursor/nuget-net10-target-a521
Sep 20, 2026
Merged

kblok merged 1 commit into
mainfrom
cursor/nuget-net10-target-a521

Conversation

@kblok

@kblok kblok commented Sep 20, 2026 •

Copy link
Copy Markdown
Member

NuGet.org labels a package with the lowest net* TFM it ships. TypeSafe.AI.Sdk targeted net10.0;net8.0;netstandard2.0, so the gallery header showed .NET 8.0 even though a dedicated net10.0 build was included.

This drops the net8.0 target so the package is marked .NET 10.0, while keeping netstandard2.0 for older runtimes. CI/publish/pages no longer install the .NET 8 SDK.

Verification

  • dotnet test -c Release: 73 unit tests passed (2 live integration tests skipped without TYPESAFE_API_KEY)
  • Packed nupkg contains lib/net10.0/ and lib/netstandard2.0/ only (no lib/net8.0/)
  • net10.0 assembly advertises .NETCoreApp,Version=v10.0

After merge

Publish a new version (for example v0.3.0) so nuget.org picks up the updated TFMs. Existing 0.1.0 / 0.2.0 packages cannot change.

Open in Web Open in Cursor 

NuGet.org shows the lowest net* TFM in the package header, so shipping
net8.0 made TypeSafe.AI.Sdk appear as a .NET 8 package. Target net10.0
and netstandard2.0 instead, and stop installing the .NET 8 SDK in CI.

Co-authored-by: Darío Kondratiuk <dariokondratiuk@gmail.com>
@kblok
kblok marked this pull request as ready for review September 20, 2026 19:16
@kblok
kblok merged commit feda524 into main Sep 20, 2026
1 check 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.

2 participants