Skip to content

2.21.0: .NET 10 and .NET 11, and the netstandard2.0 build for .NET 8 and 9 - #164

Merged
Laurianti merged 3 commits into
mainfrom
dotnet10-and-11
Nov 12, 2026
Merged

Laurianti merged 3 commits into
mainfrom
dotnet10-and-11

Conversation

@Laurianti

Copy link
Copy Markdown
Member

ChromaDotNet.Client and ChromaDotNet.Client.DependencyInjection 2.21.0: the builds for .NET 10 instead of .NET 8, the tests on .NET 10 and .NET 11, and a .NET Standard 2.0 build with the API and the behavior of the others, for the applications on .NET 8 and 9.

.NET 8 and .NET 9 went out of support on 10 November 2026, and .NET 11 came out the same day. The packages now build for net10.0, net462 and netstandard2.0. Applications on .NET 10 and later take net10.0, as those on .NET 11 do. Applications on .NET 8 and 9 take netstandard2.0, which gains what the net8.0 build had:

  • the embedding generators of Microsoft.Extensions.AI 9.5.0, which has a netstandard2.0 build. Every build has the same public API, checked by the analyzer with one set of PublicAPI files. The 6 entries of the generators, released in the net8.0 and net462 builds, move to the main PublicAPI.Shipped.txt;
  • the buckets of db.client.operation.duration advised by the semantic conventions, with System.Diagnostics.DiagnosticSource 9.0.20, whose netstandard2.0 build has InstrumentAdvice;
  • for the HttpClient of a client created without one, the SocketsHttpHandler with a PooledConnectionLifetime of two minutes, and DateOnly in ChromaMetadataConvert. .NET Standard 2.0 has neither type. The build finds them in the runtime by their names, and reads their members next to Type.GetType with constant names, so that trimming and NativeAOT keep them. .NET Framework has neither type, and keeps the HttpClientHandler.

The public API of every application stays the same or grows, so this is a minor version.

What changes for applications:

  • On .NET 8 and 9, Microsoft.Extensions.AI.Abstractions 9.5.0 and DiagnosticSource 9.0.20 come as with the net8.0 build. System.Text.Json 8.0.6 and System.Memory 4.5.5 now come with them.
  • On .NET Core 3.1 to 7, they now get the embedding generators, and the warning of DiagnosticSource 9 that it does not support these versions. SuppressTfmSupportBuildWarnings turns the warning off.
  • The .NET Standard 2.0 build cannot be marked IsAotCompatible. The net10.0 build is.
  • The DependencyInjection package builds for net10.0 and netstandard2.0, as it built for net8.0 and netstandard2.0.

CI:

  • DOTNET_VERSION is 10.0.x, and the tests and the samples build for net10.0.
  • A new job, .NET 11.0, builds the tests for net11.0 with -p:TestTargetFramework=net11.0, as an application on .NET 11 is built. dotnet test -f net11.0 does not restore a framework that the project does not declare. The job runs the tests against Chroma 1.5.9 in both passes, publishes Samples/ChromaDB.Client.TrimmingTest for .NET 11 with trimming and with NativeAOT, every warning an error, and runs it. Publish waits for the job. The version is written once, in its matrix.
  • The step with -warnaserror builds the applications that now take netstandard2.0, on .NET 8 and 9, instead of .NET 6 and 7.
  • TrimmingTest reads a DateOnly back, also as an array and a list.

Tests:

  • HandlerOfTheDefaultHttpClient checks the SocketsHttpHandler and its two minutes on .NET, and the HttpClientHandler on .NET Framework 4.8.
  • DateOnlyAsADate now also runs on the netstandard2.0 build, with lists and a text that is not a date.
  • The tests of the embedding generators and of the buckets no longer skip netstandard2.0.

In our tests on 12 November 2026, run as the CI runs them:

  • In Linux containers, with SDK 10.0.404, as DOTNET_VERSION 10.0.x installs, and 11.0.100 for the job .NET 11.0, every test passed:
    • on Chroma 1.5.9 (2,962 of 2,972 in each pass, 10 skipped), with the pack, the applications on .NET 8 and 9, and the netstandard2.0 build;
    • on 0.4.10, 0.4.15 and 0.4.23 with the v1 API, and on 1.0.0;
    • on VecturaDB 1.0.0-preview.8;
    • built for .NET 11 against 1.5.9.
  • The trimmed and the NativeAOT app ran, 25 steps of 25, built for .NET 10 and for .NET 11.
  • FrameworkTests passed on .NET Framework 4.8 on Windows, 92 of 92.
  • The suite passed against the netstandard2.0 build on the .NET 8.0.34 runtime (2,962 of 2,972, 10 skipped). The app published for .NET 8 with trimming and with NativeAOT, every warning an error, ran on that build, 25 steps of 25.
  • Without each change, its test failed on the netstandard2.0 build on .NET 8: without DateOnly found by name, DateOnlyAsADate; with the HttpClientHandler of before, HandlerOfTheDefaultHttpClient.
  • Chroma 0.5.15, 0.5.16, 0.5.20, 0.6.3 and latest run only in the CI of this pull request.

…d the behavior of net10.0

.NET 8 and .NET 9 went out of support on 10 November 2026. The packages
build for net10.0, net462 and netstandard2.0, and applications on .NET 8
and 9 now take netstandard2.0, which gains what net8.0 had:
- the embedding generators of Microsoft.Extensions.AI 9.5.0, which has a
  netstandard2.0 build: the same public API on every build, in one set of
  PublicAPI files;
- the advised buckets of db.client.operation.duration, with
  System.Diagnostics.DiagnosticSource 9.0.20, which has InstrumentAdvice;
- the SocketsHttpHandler with a PooledConnectionLifetime of two minutes,
  for the HttpClient of a client created without one, and DateOnly in
  ChromaMetadataConvert. netstandard2.0 has neither type: the build finds
  them in the runtime by their names, with their members read next to
  Type.GetType with constant names, so that trimming and NativeAOT keep
  them. .NET Framework has neither, and keeps the HttpClientHandler.

Version 2.21.0: the public API of every application stays the same or
grows.
…NET 8 and 9

DOTNET_VERSION is 10.0.x, and the tests and the samples build for
net10.0. The job .NET 11.0 builds the tests for net11.0 with
-p:TestTargetFramework, as an application on .NET 11 is built, because
dotnet test -f does not restore a framework the project does not
declare. It runs them against Chroma 1.5.9 in both passes, and publishes
and runs the trimmed and the NativeAOT app for .NET 11. Publish waits
for it. The step with -warnaserror builds the applications that now take
netstandard2.0, on .NET 8 and 9 instead of .NET 6 and 7. The trimmed and
NativeAOT app reads a DateOnly back, also as an array and a list.
… .NET 11

docs/platforms.md, embeddings.md, observability.md, where the view for
the netstandard2.0 build is no longer needed, about-this-fork.md,
COMPATIBILITY.md and CONTRIBUTING.md.
@Laurianti
Laurianti requested a review from a team as a code owner November 12, 2026 15:56
@Laurianti
Laurianti merged commit be7f136 into main Nov 12, 2026
17 checks passed
@Laurianti
Laurianti deleted the dotnet10-and-11 branch November 12, 2026 16:20
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