Repository navigation
2.21.0: .NET 10 and .NET 11, and the netstandard2.0 build for .NET 8 and 9 - #164
Merged
Merged
Conversation
…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.
ambergrove
approved these changes
Nov 12, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:
PublicAPI.Shipped.txt;db.client.operation.durationadvised by the semantic conventions, with System.Diagnostics.DiagnosticSource 9.0.20, whose netstandard2.0 build hasInstrumentAdvice;HttpClientof a client created without one, theSocketsHttpHandlerwith aPooledConnectionLifetimeof two minutes, andDateOnlyinChromaMetadataConvert. .NET Standard 2.0 has neither type. The build finds them in the runtime by their names, and reads their members next toType.GetTypewith constant names, so that trimming and NativeAOT keep them. .NET Framework has neither type, and keeps theHttpClientHandler.The public API of every application stays the same or grows, so this is a minor version.
What changes for applications:
SuppressTfmSupportBuildWarningsturns the warning off.IsAotCompatible. The net10.0 build is.CI:
DOTNET_VERSIONis 10.0.x, and the tests and the samples build for net10.0.-p:TestTargetFramework=net11.0, as an application on .NET 11 is built.dotnet test -f net11.0does not restore a framework that the project does not declare. The job runs the tests against Chroma 1.5.9 in both passes, publishesSamples/ChromaDB.Client.TrimmingTestfor .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.-warnaserrorbuilds the applications that now take netstandard2.0, on .NET 8 and 9, instead of .NET 6 and 7.TrimmingTestreads aDateOnlyback, also as an array and a list.Tests:
HandlerOfTheDefaultHttpClientchecks theSocketsHttpHandlerand its two minutes on .NET, and theHttpClientHandleron .NET Framework 4.8.DateOnlyAsADatenow also runs on the netstandard2.0 build, with lists and a text that is not a date.In our tests on 12 November 2026, run as the CI runs them:
DOTNET_VERSION10.0.x installs, and 11.0.100 for the job .NET 11.0, every test passed:DateOnlyfound by name,DateOnlyAsADate; with theHttpClientHandlerof before,HandlerOfTheDefaultHttpClient.latestrun only in the CI of this pull request.