What chroma-core/chroma shipped
Written by FoxPlug from public releases; not affiliated with Trychroma. An automatic summary of the public release, pull request and commit data of github.com/chroma-core/chroma. Trychroma did not write it and does not use or endorse FoxPlug. Every line links to the public change it describes.
Get a weekly update like this for your product, free
Week of September 21, 2026
What shipped
- Foundation catalog API now supports creating, listing, and describing a tenant's Foundations with product identity and database association. Pull request #7713
- API routes now accept tenant and Foundation identifiers in the request path to support multiple private memory resources per tenant. Pull request #7712
- MCP clients can select a specific Foundation through per-Foundation path routing at
/mcp/tenants/{tenant}/foundations/{foundation}. Pull request #7714 - Agent query spend is now debited against Foundation price cards after response streams complete. Pull request #7759
- Foundation creation is paused during migration to prevent new Foundations from being missed when registering the product-record table. Pull request #7782
- Metadata service now properly returns segment row read errors instead of crashing. Pull request #7785
- Benchmark dataset cache now flushes file handles before renaming cached files to prevent stale data. Pull request #7717
- Exponential backoff test now bounds timing by elapsed time rather than fixed duration for more reliable results. Pull request #7718
Why it matters
This week adds multi-tenant Foundation support with explicit routing and billing integration. The catalog-backed API lets tenants manage multiple private databases, while spend tracking ensures accurate pricing against Foundation price cards. Bug fixes prevent data loss and billing errors during this expansion.
Changelog entry
- foundation-api: Add Foundation catalog creation, listing, and description endpoints backed by product catalog Pull request #7713
- foundation-api: Support explicit tenant and Foundation selection in API request paths Pull request #7712
- foundation-api: Add per-Foundation MCP endpoint routing at
/mcp/tenants/{tenant}/foundations/{foundation}Pull request #7714 - foundation-api: Debit agent query spend against Foundation price cards after response completion Pull request #7759
- foundation-api: Pause Foundation creation during product-record table migration Pull request #7782
- sysdb: Return segment row read errors instead of crashing metadata service Pull request #7785
- benchmark: Flush cached dataset file handles before renaming Pull request #7717
- wal3: Bound exponential backoff test by elapsed time instead of fixed duration Pull request #7718
[0] 1.5.10.dev301 released. Foundation catalog API now live: create, list, describe Foundations. Multi-tenant routing supported. Spend tracking integrated. Docs updated.
[0] 1.5.10.dev301 released. Major Foundation management features now available: create and manage multiple private memory resources per tenant with catalog-backed APIs. Foundation-specific routing through /mcp/tenants/{tenant}/foundations/{foundation}. Agent query spending is now tracked and debited against Foundation price cards. Documentation updated and billing bugs fixed.
Week of September 14, 2026
What shipped
- Float metadata values now survive SQLite log round trips with full precision, fixing equality filters that would miss records after log replay. Pull request #7755
- Work queue service GetWork now paces results using optional token bucketing while preserving FIFO and failure filtering. Pull request #7748
- Append operations now expose contention as structured AppendOutcome, distinguishing between committed, contention, and independent failures. Pull request #7653
- SysDB now supports looking up databases by ID through a new GET endpoint with tenant isolation. Pull request #7709
- SysDB database listing now properly honors limit and offset pagination parameters. Pull request #7710
- Latency measurement moved to a shared chroma-metrics crate, removing storage dependency on tracing and fastrace. Pull request #7658
- Parquet statistics disabled for opaque WAL3 body columns to reduce unnecessary metadata overhead. Pull request #7645
- Log service build configuration unified across Tilt environments by removing local overrides. Pull request #7749
- MinIO test image pinned to digest on quay.io to avoid Docker Hub rate limits and improve reproducibility. Pull request #7741
Why it matters
This week addresses core correctness issues in metadata handling and pagination, improves operational efficiency through caching and token pacing, and refactors internal code organization. These changes strengthen reliability for users relying on metadata queries and work scheduling while reducing infrastructure friction.
Changelog entry
- Fixed: Float metadata values now preserve precision through SQLite log JSON round trips Pull request #7755
- Enhanced: Work queue service GetWork results now paced with optional token bucketing Pull request #7748
- Enhanced: Append contention exposed as structured AppendOutcome instead of error interpretation Pull request #7653
- Enhanced: SysDB supports database lookup by ID with tenant isolation Pull request #7709
- Fixed: SysDB database listing now respects limit and offset pagination Pull request #7710
- Refactored: Operation latency measurement moved to shared chroma-metrics crate Pull request #7658
- Optimized: Parquet statistics disabled for WAL3 opaque body columns Pull request #7645
- Fixed: MinIO test image pinned to digest for reproducibility Pull request #7741
Week's updates: float metadata precision fixed for log round trips, work queue pacing added, database pagination honored, and append contention now structured for clearer error handling.
This week's updates improve core reliability and efficiency: metadata floats now maintain precision through database round trips, work queues pace results with token bucketing, database pagination is properly enforced, and append contention is exposed as structured outcomes. Plus internal refactoring: latency measurement moved to shared metrics, agent request prefixes cached, and test infrastructure pinned for reproducibility.