●Change8

1.0.13

📦 chromaView on GitHub →
✨ 8 features🐛 14 fixes🔧 4 symbols

Summary

Version 1.0.13 focuses heavily on performance improvements, stability fixes across the Rust log service and WAL3 reader, and introduces a new JavaScript client alongside documentation updates.

Migration Steps

  1. If you rely on SQLite $contains filters, note that _ and % characters are now properly escaped.

✨ New Features

  • Introduced a new JavaScript Client.
  • Added parameters to GetCollections to include soft deleted items and filter by collection IDs.
  • Implemented caching for manifests used for pull logs.
  • Added support for asynchronous dirty log rollup refactoring.
  • Enabled wal3 for the default tenant.
  • Added a grace period for GCv2 transitioning soft deleted collections to hard deleted.
  • Added a tool to purge a collection from the dirty log.
  • Removed CoreML as a provider for default embedding functions (EF).

🐛 Bug Fixes

  • Fixed Rust log service fork offsets being off by one.
  • Correctly updated collections.num_versions upon compaction flush.
  • Fixed a validation bug.
  • Resolved an issue where creating and deleting many collections prevented dirty log rollup.
  • Fixed a bug in wal3 records-based pruning.
  • Removed masked error from ForkLogs.
  • Ensured the cached manifest can satisfy a pull-logs request.
  • Sealed collections on fork in the go log.
  • Properly escaped _ and escaped % rather than stripping for SQLite $contains filter.
  • Fixed concurrency bug in test_cross_version_persist.
  • Fixed an out-of-bounds error (obo) in the wal3 reader (hotfix applied).
  • Fixed test filtering flake caused by wildcard handling change.
  • Fixed test parallelization issues.
  • Populated client arguments from deprecated arguments.

🔧 Affected Symbols

collections.num_versionsGetCollectionswal3 readerSQLite $contains filter