Quivr 2.0.2
2.0.2 moves the search database to Weaviate 1.39.14. It changes no API, no configuration and no stored data. Upgrade any 2.0.x installation to it.
What Weaviate 1.39.14 fixes for Quivr
- Filtered searches no longer fail at random. Quivr filters every vector and hybrid search to the scope of the request. Weaviate's default filtering strategy could crash such a search on a node of the vector graph with more links than expected, and the search then returned an error.
- Security: CVE-2026-63209, in the compression library.
- Less memory.
- Quivr compresses its vectors. Compressed indexes now drop the uncompressed vector cache they no longer use, which can save gigabytes on a large index.
- Weaviate also stops keeping memory it never frees when writing to its in-memory tables.
- Safer restarts. A crash right after a shutdown could leave a keyword-search file empty, and the database would then not start without a manual repair. Startup and shutdown are also faster.
Results do not change. The hybrid search changes in 1.39.14 only affect offset paging and nearText queries, and Quivr uses neither.
Upgrade from 2.0.0 or 2.0.1
- Back up the search database volume.
- Deploy the 2.0.2 images and the new Weaviate pin from
deploy/infrastructure.json, or the 2.0.2 compose bundle attached to this release for a single machine. - Keep the same Weaviate volume.
This is a patch upgrade within one Weaviate minor version: no re-indexing and no Quivr migration. The test that upgrades a 1.37.15 volume through 1.38.20 to 1.39.14, then checks lexical, semantic and hybrid search, passes on this release.
The release images are signed and carry SBOMs, as described in Security of Quivr releases.