Repository navigation
Releases: ChromaDotNet/ChromaDB.Testcontainers
Release list
v0.2.0
Minor release of ChromaDotNet.Testcontainers, with breaking changes. The module is the one of testcontainers/testcontainers-dotnet#1784, aligned with the conventions of that repository.
dotnet add package ChromaDotNet.Testcontainers
Breaking changes
ChromaBuilder.ChromaHttpPortis nowChromaBuilder.ChromaPort. The value is still 8000.- The obsolete parameterless constructor of
ChromaBuilderand the obsolete constantChromaBuilder.ChromaImageare removed. Pass the image to the constructor:new ChromaBuilder("chromadb/chroma:1.5.9").
Changes
- Tested with ChromaDotNet.Client 2.18.1, on Chroma 0.4.10 to 1.5.9.
- Synced with testcontainers-dotnet: the module is the same, byte for byte, as in the pull request.
Package: ChromaDotNet.Testcontainers 0.2.0
v0.1.8
Patch release of ChromaDotNet.Testcontainers: the same code as 0.1.7.
dotnet add package ChromaDotNet.Testcontainers
Changes
- The new icon of ChromaDotNet, without the colors of Chroma: the dots of the C in teal and the final dot in indigo, on a dark tile.
- The package description ends with: Independent project. Not affiliated with, endorsed by or sponsored by Chroma Inc. CHROMA is a registered trademark of Chroma Inc., used here only to describe compatibility.
Package: ChromaDotNet.Testcontainers 0.1.8
v0.1.7
Patch release of ChromaDotNet.Testcontainers: tests.
dotnet add package ChromaDotNet.Testcontainers
Changes
- Tested with ChromaDotNet.Client 2.11.0.
- Synced with testcontainers-dotnet; the module is unchanged.
Package: ChromaDotNet.Testcontainers 0.1.7
v0.1.6
Patch release of ChromaDotNet.Testcontainers: tests.
dotnet add package ChromaDotNet.Testcontainers
Changes
- Tested with ChromaDotNet.Client 2.10.0.
- Synced with testcontainers-dotnet; the module is unchanged.
Package: ChromaDotNet.Testcontainers 0.1.6
v0.1.5
Patch release of ChromaDotNet.Testcontainers: README and tests.
dotnet add package ChromaDotNet.Testcontainers
Changes
- README: shorter sentences, with the same facts and links.
- Tested with ChromaDotNet.Client 2.9.2.
- Synced with testcontainers-dotnet; the module is unchanged.
Package: ChromaDotNet.Testcontainers 0.1.5
v0.1.4
Patch release of ChromaDotNet.Testcontainers: README and tests.
dotnet add package ChromaDotNet.Testcontainers
Changes
- README: the ChromaDotNet logo and the website at the top, and the repository of ChromaDotNet.Client next to its package.
- Tested with ChromaDotNet.Client 2.9.1.
- Synced with testcontainers-dotnet; the module is unchanged.
Package: ChromaDotNet.Testcontainers 0.1.4
v0.1.3
Patch release of ChromaDotNet.Testcontainers: the README on NuGet matches ChromaDotNet.Client 2.8.0.
dotnet add package ChromaDotNet.Testcontainers
Changes
- README example: uses the
Asyncmethods of ChromaDotNet.Client 2.8.0. - README: names
GetBaseAddress()andChromaBuilder.ChromaHttpPort, and links the documentation page with an absolute URL.
Package: ChromaDotNet.Testcontainers 0.1.3
v0.1.2
Patch release of ChromaDotNet.Testcontainers: synced with testcontainers-dotnet, and a package with the ChromaDotNet logo.
dotnet add package ChromaDotNet.Testcontainers
Changes
- Synced with the latest changes of testcontainers-dotnet.
- Tested with ChromaDotNet.Client 2.8.0.
- Package: the ChromaDotNet logo as its icon, and a description that says that the project is a community project, not affiliated with Chroma.
Package: ChromaDotNet.Testcontainers 0.1.2
v0.1.1
Patch release of ChromaDotNet.Testcontainers: the module is kept in step with the one proposed to testcontainers-dotnet.
dotnet add package ChromaDotNet.Testcontainers
Changes
- In step with testcontainers-dotnet: the module and its project file are synced from the version proposed there. The README says how.
- The example of the documentation page (
docs/modules/chroma.md) uses ChromaDotNet.Client 2.6.0 and its collection client.
Package: ChromaDotNet.Testcontainers 0.1.1
v0.1.0
First release of ChromaDotNet.Testcontainers: a Testcontainers for .NET module for Chroma, to start a throwaway Chroma container in your tests.
dotnet add package ChromaDotNet.Testcontainers
New
ChromaBuilderandChromaContainer, in theTestcontainers.Chromanamespace.GetConnectionString()gives the base address of the Chroma API, likehttp://localhost:32768/.- Ready when Chroma answers: the module waits for the heartbeat of the v2 API, or of the v1 API on the releases before 0.5.16, so it works with any Chroma image.
- Tested on nine Chroma releases, from 0.4.10 to 1.5.9, and on the latest image: the container is ready on each of them. The example with ChromaDotNet.Client runs on 1.5.9.
Package: ChromaDotNet.Testcontainers 0.1.0