v3.4.2 ruvector-wasm-v2.3.1

high risk

ruvnet/RuVectorOct 2, 2026 → Oct 6, 20264 days between releases

What's New

Fixes critical IndexedDB persistence bugs and adds versioned snapshots.

Breaking Changes

  • VectorDB.loadFromIndexedDB is no longer a stub; it is now a required static async method
  • saveToIndexedDB is commit-gated and can now reject on quota exceeded or abort
  • Added setDbName API; instances now save under a random name by default unless named

New Features

  • Versioned snapshot storage for deterministic database reloading
  • HNSW graph rebuilding on load from snapshot
  • Database naming and retrieval via setDbName API
  • Transaction commit gating with error handling for IndexedDB
  • Validation for invalid or corrupt payloads during load

Improvements

  • Test coverage increased with 16 wasm-bindgen-test browser tests
  • Added ADR-200 documentation for IndexedDB persistence contract

Bug Fixes

  • Fixed saveToIndexedDB to actually commit data after transaction completion
  • Implemented VectorDB.loadFromIndexedDB(name) as a static async method
  • Fixed unimplemented loadFromIndexedDB behavior

Upgrade Notes

Update existing loadFromIndexedDB calls as the method is now fully implemented and static. Call setDbName if you require deterministic database naming across sessions. Handle potential rejections from saveToIndexedDB for quota or abort errors.

The Two Releases

v3.4.2

v3.4.2

Oct 2, 2026· 19 days ago

Focuses on performance optimizations for database operations, specifically indexing and vector search, alongside local disk caching and documentation updates.

Full release notes
ruvector-wasm-v2.3.1

ruvector-wasm 2.3.1 — IndexedDB persistence fix

Oct 6, 2026· 16 days ago

Fixes critical IndexedDB persistence bugs where `saveToIndexedDB` reported success without saving data and `loadFromIndexedDB` was unimplemented. Now supports versioned snapshots, transaction commit gating, and deterministic database reloading.

Full release notes