[anush008]

Gist

The Chroma source now calls the Chroma HTTP API directly, in place of the chroma-go client. This improves data precision and adds Chroma to the standalone binary because it no longer needs CGO..

Fixes

• Records with a null document, array metadata don't err.
• Integer metadata stays an integer in Qdrant. Before, it became a float.
• Chroma URIs are now migrated, to --qdrant.uri-field (default uri).

Improvements

• The migration fails if the target has fewer points than the source, and keeps the offsets for a resume.
• Chroma requests retry network errors, 429, and 5xx responses.
• Resume offsets use the Chroma collection ID, so collections with the same name in different databases stay apart.
• Sparse vectors are skipped with a warning. Sparse vectors are Chroma Cloud only and we don't have access.

[anush008]

@generall, the CI failure is unrelated.

Trivy Vulnerability Scanner

2026-10-27T05:31:18Z FATAL Fatal error run error: init error: DB error: failed to download vulnerability DB: OCI artifact error: failed to download vulnerability DB: failed to download artifact from any source: 1 error occurred:
* OCI repository error: 1 error occurred:
* GET https://public.ecr.aws/v2/aquasecurity/trivy-db/manifests/2: TOOMANYREQUESTS: Data limit exceeded

Could you please bypass the CI requirements and merge?