Skip to content

Releases

ChromaDotNet.Local 1.5.9.1-preview.7

Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Oct 22:20
4c81b50

Preview of ChromaDotNet.Local 1.5.9.1-preview.7, the base without an engine. 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.

ChromaDotNet.Local starts the server of an engine package as a child
process on 127.0.0.1, for ChromaDotNet.Client, and stops it with Dispose or when the application ends. An application references an
engine, which brings the base:

In this preview, ChromaDotNet.Local depends on ChromaDotNet.Client 2.18.0 or later: an application that references an earlier
ChromaDotNet.Client updates it, or the restore fails with NU1605.

From 1.5.9.1-preview.5:

  • ChromaDotNet.Local has no engine of its own. An application on ChromaDotNet.Local 1.5.9.1-preview.5 adds ChromaDotNet.Local.ChromaDB,
    and updates ChromaDotNet.Local to 1.5.9.1-preview.7 or removes it: left at 1.5.9.1-preview.5, the restore fails with NU1605. Its
    code stays the same. Without an engine, the build of an application or of a project of tests gives the warning CDNL001, and
    ChromaLocalServer.StartAsync fails with a message that names the two packages, unless ChromaLocalOptions.ExecutablePath names an
    executable.
  • With the two engines in one application, ChromaLocalOptions.Engine chooses the one of each server.
  • ChromaLocalServer.Engine and ChromaLocalServer.EngineVersion say the engine of the server. ChromaLocalServer.ChromaVersion is
    obsolete.
  • The guard of Linux and macOS, which stops the server when the application is killed, is in this package.

The package of this release is signed with Sigstore, with its build provenance:

cosign verify-blob --bundle ChromaDotNet.Local.1.5.9.1-preview.7.nupkg.sigstore.json --certificate-identity-regexp '^https://github[.]com/ChromaDotNet/ChromaDB[.]Local/[.]github/workflows/ci[.]yml@refs/tags/' --certificate-oidc-issuer https://token.actions.githubusercontent.com ChromaDotNet.Local.1.5.9.1-preview.7.nupkg
gh attestation verify ChromaDotNet.Local.1.5.9.1-preview.7.nupkg --repo ChromaDotNet/ChromaDB.Local --signer-workflow ChromaDotNet/ChromaDB.Local/.github/workflows/ci.yml --source-ref refs/tags/v1.5.9.1-preview.7

ChromaDotNet.Local 1.5.9.1-preview.6

Pre-release

Choose a tag to compare

@github-actions github-actions released this 25 Oct 08:00
e6de64a

Preview of ChromaDotNet.Local 1.5.9.1-preview.6, the base without an engine. Community project, not affiliated with Chroma.

ChromaDotNet.Local starts the server of an engine package as a child
process on 127.0.0.1, for ChromaDotNet.Client, and stops it with Dispose or when the application ends. An application references an
engine, which brings the base:

In this preview:

  • ChromaDotNet.Local has no engine of its own. An application on ChromaDotNet.Local 1.5.9.1-preview.5 adds ChromaDotNet.Local.ChromaDB,
    and updates ChromaDotNet.Local to 1.5.9.1-preview.6 or removes it: left at 1.5.9.1-preview.5, the restore fails with NU1605. Its
    code stays the same. Without an engine, the build of an application or of a project of tests gives the warning CDNL001, and
    ChromaLocalServer.StartAsync fails with a message that names the two packages, unless ChromaLocalOptions.ExecutablePath names an
    executable.
  • With the two engines in one application, ChromaLocalOptions.Engine chooses the one of each server.
  • ChromaLocalServer.Engine and ChromaLocalServer.EngineVersion say the engine of the server. ChromaLocalServer.ChromaVersion is
    obsolete.
  • The guard of Linux and macOS, which stops the server when the application is killed, is in this package.

The package of this release is signed with Sigstore, with its build provenance:

cosign verify-blob --bundle ChromaDotNet.Local.1.5.9.1-preview.6.nupkg.sigstore.json --certificate-identity-regexp '^https://github[.]com/ChromaDotNet/ChromaDB[.]Local/[.]github/workflows/ci[.]yml@refs/tags/' --certificate-oidc-issuer https://token.actions.githubusercontent.com ChromaDotNet.Local.1.5.9.1-preview.6.nupkg
gh attestation verify ChromaDotNet.Local.1.5.9.1-preview.6.nupkg --repo ChromaDotNet/ChromaDB.Local --signer-workflow ChromaDotNet/ChromaDB.Local/.github/workflows/ci.yml --source-ref refs/tags/v1.5.9.1-preview.6

ChromaDotNet.Local.VecturaDB 1.0.0-preview.3.1

Choose a tag to compare

@github-actions github-actions released this 25 Oct 23:10
4c81b50

Preview of ChromaDotNet.Local.VecturaDB 1.0.0-preview.3.1, with VecturaDB 1.0.0-preview.3, for ChromaDotNet.Local 1.5.9.1-preview.7. 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.

ChromaDotNet.Local.VecturaDB starts VecturaDB. VecturaDB is a
vector database compatible with the Chroma API, bringing Chroma Cloud's features to open source: sparse vectors, BM25 and the Search
API. The first start downloads the executable of its platform from the GitHub release
v1.0.0-preview.3 of VecturaDB, for Windows x64, Linux x64 and arm64,
macOS x64 and arm64, into the cache of the user. The package has the SHA-256 hash of each executable, the digest GitHub gives the
file: it checks it after the download and before each start. The notices of VecturaDB are in THIRD-PARTY-NOTICES.md, in the package.

The package of this release is signed with Sigstore, with its build provenance:

cosign verify-blob --bundle ChromaDotNet.Local.VecturaDB.1.0.0-preview.3.1.nupkg.sigstore.json --certificate-identity-regexp '^https://github[.]com/ChromaDotNet/ChromaDB[.]Local/[.]github/workflows/ci[.]yml@refs/tags/' --certificate-oidc-issuer https://token.actions.githubusercontent.com ChromaDotNet.Local.VecturaDB.1.0.0-preview.3.1.nupkg
gh attestation verify ChromaDotNet.Local.VecturaDB.1.0.0-preview.3.1.nupkg --repo ChromaDotNet/ChromaDB.Local --signer-workflow ChromaDotNet/ChromaDB.Local/.github/workflows/ci.yml --source-ref refs/tags/vecturadb-v1.0.0-preview.3.1

ChromaDotNet.Local.ChromaDB 1.5.9.1-preview.7

Choose a tag to compare

@github-actions github-actions released this 25 Oct 23:17
4c81b50

Preview of ChromaDotNet.Local.ChromaDB 1.5.9.1-preview.7, with Chroma 1.5.9 (the Chroma CLI cli-1.4.4), for ChromaDotNet.Local
1.5.9.1-preview.7. 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.

The packages are on NuGet: ChromaDotNet.Local.ChromaDB, with the
ChromaDotNet.Local.ChromaDB.Runtime package of each platform, which has its executable. With
<ChromaDotNetLocalChromaDBDownload>true</ChromaDotNetLocalChromaDBDownload> in the project, the executables are not in the output,
and the first start downloads the one of its platform from this release.

In this preview, ChromaDotNet.Local.ChromaDB depends on ChromaDotNet.Local 1.5.9.1-preview.7, with ChromaDotNet.Client 2.18.0 or
later. The executables are those of 1.5.9.1-preview.6, named chromadb. The guard of Linux and macOS is in ChromaDotNet.Local.

From 1.5.9.1-preview.5, Chroma is an engine of ChromaDotNet.Local, the base without an engine. ChromaDotNet.Local.ChromaDB takes the
place of ChromaDotNet.Local 1.5.9.1-preview.5, ChromaDotNet.Local.Core and the ChromaDotNet.Local.Runtime packages: an application on
them references ChromaDotNet.Local.ChromaDB in their place, and its code stays the same. A reference to ChromaDotNet.Local
1.5.9.1-preview.5 left next to it fails at the restore with NU1605: update it to 1.5.9.1-preview.7, or remove it.

The files of this release are the executables of the runtime packages, compressed with gzip. ChromaDotNet.Local.ChromaDB has the
SHA-256 hash of each of them, uncompressed, and checks it after the download and before each start. To check the files yourself:

sha256sum -c SHA256SUMS
cosign verify-blob --bundle chromadb-linux-x64.gz.sigstore.json --certificate-identity-regexp '^https://github[.]com/ChromaDotNet/ChromaDB[.]Local/[.]github/workflows/ci[.]yml@refs/tags/' --certificate-oidc-issuer https://token.actions.githubusercontent.com chromadb-linux-x64.gz
gh attestation verify chromadb-linux-x64.gz --repo ChromaDotNet/ChromaDB.Local --signer-workflow ChromaDotNet/ChromaDB.Local/.github/workflows/ci.yml --source-ref refs/tags/chromadb-v1.5.9.1-preview.7

On Windows and macOS the executables are those of the GitHub release of the Chroma CLI, checked against its digests. On Linux they
are built from its tag, with no change to the code, for glibc 2.28 and later; two builds give the same bytes.

ChromaDotNet.Local.ChromaDB 1.5.9.1-preview.6

Choose a tag to compare

@github-actions github-actions released this 25 Oct 10:05
793bb2b

Preview of ChromaDotNet.Local.ChromaDB 1.5.9.1-preview.6, with Chroma 1.5.9 (the Chroma CLI cli-1.4.4), for ChromaDotNet.Local
1.5.9.1-preview.6. Community project, not affiliated with Chroma.

The packages are on NuGet: ChromaDotNet.Local.ChromaDB, with the
ChromaDotNet.Local.ChromaDB.Runtime package of each platform, which has its executable. With
<ChromaDotNetLocalChromaDBDownload>true</ChromaDotNetLocalChromaDBDownload> in the project, the executables are not in the output,
and the first start downloads the one of its platform from this release.

In this preview:

  • Chroma is an engine of ChromaDotNet.Local 1.5.9.1-preview.6, the base without an engine. ChromaDotNet.Local.ChromaDB takes the
    place of ChromaDotNet.Local 1.5.9.1-preview.5, ChromaDotNet.Local.Core and the ChromaDotNet.Local.Runtime packages: an application
    on them references ChromaDotNet.Local.ChromaDB in their place, and its code stays the same. A reference to ChromaDotNet.Local
    1.5.9.1-preview.5 left next to it fails at the restore with NU1605: update it to 1.5.9.1-preview.6, or remove it.
  • The executables are those of 1.5.9.1-preview.5, named chromadb. The guard of Linux and macOS is in ChromaDotNet.Local.

The files of this release are the executables of the runtime packages, compressed with gzip. ChromaDotNet.Local.ChromaDB has the
SHA-256 hash of each of them, uncompressed, and checks it after the download and before each start. To check the files yourself:

sha256sum -c SHA256SUMS
cosign verify-blob --bundle chromadb-linux-x64.gz.sigstore.json --certificate-identity-regexp '^https://github[.]com/ChromaDotNet/ChromaDB[.]Local/[.]github/workflows/ci[.]yml@refs/tags/' --certificate-oidc-issuer https://token.actions.githubusercontent.com chromadb-linux-x64.gz
gh attestation verify chromadb-linux-x64.gz --repo ChromaDotNet/ChromaDB.Local --signer-workflow ChromaDotNet/ChromaDB.Local/.github/workflows/ci.yml --source-ref refs/tags/chromadb-v1.5.9.1-preview.6

On Windows and macOS the executables are those of the GitHub release of the Chroma CLI, checked against its digests. On Linux they
are built from its tag, with no change to the code, for glibc 2.28 and later; two builds give the same bytes.

ChromaDotNet.Local 1.5.9.1-preview.5

Pre-release

Choose a tag to compare

@github-actions github-actions released this 21 Oct 08:42
98e0a09

Preview of ChromaDotNet.Local 1.5.9.1-preview.5, with Chroma 1.5.9 (the Chroma CLI cli-1.4.4). Community project, not affiliated with Chroma.

The packages are on NuGet: ChromaDotNet.Local, with the executables of
every platform; ChromaDotNet.Local.Core, without them, which
downloads the one of its platform from this release at the first start; and the ChromaDotNet.Local.Runtime package of each platform.

In this preview:

  • The output of Chroma is read on threads of each server, not on the thread pool: on Windows many servers in one process no longer
    make the start wait past StartupTimeout.
  • On Windows a DataPath longer than 206 characters throws a PathTooLongException before anything starts: with a longer one Chroma
    did not load the index of a collection after a restart.
  • The lock file of the data says "another ChromaLocalServer" only when another process holds it; other errors say what they are.
  • The cache deletes the temporary files of downloads that did not end, and gives errors with the path for a directory in place of
    an executable and for an executable deleted before the start.

The files of this release are the executables of the runtime packages, compressed with gzip. ChromaDotNet.Local.Core has the SHA-256
hash of each of them, uncompressed, and checks it after the download and before each start. To check the files yourself:

sha256sum -c SHA256SUMS
cosign verify-blob --bundle chroma-linux-x64.gz.sigstore.json --certificate-identity-regexp '^https://github.com/ChromaDotNet/ChromaDB.Local/' --certificate-oidc-issuer https://token.actions.githubusercontent.com chroma-linux-x64.gz
gh attestation verify chroma-linux-x64.gz --repo ChromaDotNet/ChromaDB.Local

On Windows and macOS the executables are those of the GitHub release of the Chroma CLI, checked against its digests. On Linux they
are built from its tag, with no change to the code, for glibc 2.28 and later; two builds give the same bytes.

ChromaDotNet.Local 1.5.9.1-preview.4

Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Oct 10:46

Preview of ChromaDotNet.Local 1.5.9.1-preview.4, with Chroma 1.5.9 (the Chroma CLI cli-1.4.4). Community project, not affiliated with Chroma.

The packages are on NuGet: ChromaDotNet.Local, with the executables of
every platform; ChromaDotNet.Local.Core, without them, which
downloads the one of its platform from this release at the first start; and the ChromaDotNet.Local.Runtime package of each platform.

The files of this release are the executables of the runtime packages, compressed with gzip. ChromaDotNet.Local.Core has the SHA-256
hash of each of them, uncompressed, and checks it after the download and before each start. To check the files yourself:

sha256sum -c SHA256SUMS
cosign verify-blob --bundle chroma-linux-x64.gz.sigstore.json --certificate-identity-regexp '^https://github.com/ChromaDotNet/ChromaDB.Local/' --certificate-oidc-issuer https://token.actions.githubusercontent.com chroma-linux-x64.gz
gh attestation verify chroma-linux-x64.gz --repo ChromaDotNet/ChromaDB.Local

On Windows and macOS the executables are those of the GitHub release of the Chroma CLI, checked against its digests. On Linux they
are built from its tag, with no change to the code, for glibc 2.28 and later; two builds give the same bytes.

ChromaDotNet.Local 1.5.9.1-preview.3

Pre-release

Choose a tag to compare

@github-actions github-actions released this 20 Oct 07:26

Preview of ChromaDotNet.Local 1.5.9.1-preview.3, with Chroma 1.5.9 (the Chroma CLI cli-1.4.4). Community project, not affiliated with Chroma.

The packages are on NuGet: ChromaDotNet.Local, with the executables of
every platform; ChromaDotNet.Local.Core, without them, which
downloads the one of its platform from this release at the first start; and the ChromaDotNet.Local.Runtime package of each platform.

The files of this release are the executables of the runtime packages, compressed with gzip. ChromaDotNet.Local.Core has the SHA-256
hash of each of them, uncompressed, and checks it after the download and before each start. To check the files yourself:

sha256sum -c SHA256SUMS
cosign verify-blob --bundle chroma-linux-x64.gz.sigstore.json --certificate-identity-regexp '^https://github.com/ChromaDotNet/ChromaDB.Local/' --certificate-oidc-issuer https://token.actions.githubusercontent.com chroma-linux-x64.gz
gh attestation verify chroma-linux-x64.gz --repo ChromaDotNet/ChromaDB.Local

On Windows and macOS the executables are those of the GitHub release of the Chroma CLI, checked against its digests. On Linux they
are built from its tag, with no change to the code, for glibc 2.28 and later; two builds give the same bytes.