The core of the v0.1.3.6 update revolves around "fixed" issues in the execution pipeline. One of the most notable improvements involves memory management during large-scale joins. In graph databases, joining multiple node sets can lead to memory spikes; Kuzu v0.1.3.6 optimizes the intermediate state handling, preventing crashes during deep traversal queries. This fix is particularly valuable for users working with massive datasets where RAM efficiency is a priority.
Your search for v0.136 is understandable, as version numbers can be confusing. However, there is no public release of the Kùzu graph database with that version number. The most recent major releases as of the time of the project's archival follow the format v0.11.x , with v0.11.3 being the final release. The project's repository was archived on October 10, 2025, and the source code is now carried on under a new moniker, "Ladybug".
: Addressed loading bugs concerning native extensions like JSON and vector search. Query Performance
: The addition of fsync() on WAL (Write-Ahead Logging) and fullfsync specifically for macOS/iOS enhances crash recovery and prevents data corruption. kuzu v0 136 fixed
Data ingestion has also seen important refinements. Previous versions occasionally encountered issues with specific CSV formatting or NULL value handling during the bulk loading process. The v0.1.3.6 patch resolves these inconsistencies, ensuring that the COPY FROM command remains robust. This means smoother transitions from flat data files to a structured graph schema without manual data scrubbing.
: Seamlessly integrates with the modern stack, including LlamaIndex, LangChain, and PyTorch Geometric. 📥 Get Started with the Fix
Scanning vertices on an active OnDiskGraph during uncommitted transactions occasionally fetched inconsistent states, breaking ACID compliance boundaries. The core of the v0
Added support for wildcard patterns in Full-Text Search (FTS) queries and implemented FTS updates.
: Fixed multi-threaded race conditions during continuous write actions, stabilizing high-volume real-time insert operations.
: Ownership of Transactions was moved from TransactionContext to TransactionManager to improve resource handling and prevent potential race conditions. This fix is particularly valuable for users working
One of the key pain points for users of Kùzu is . The database file format can change between versions, and Kùzu currently does not guarantee backward compatibility.
kuzu v0 136 fixed (primary), Kuzu v0.136 benchmark, upgrade Kuzu, Kuzu memory leak fix, Kuzu concurrency patch, Kuzu JSON parser, Kuzu migration guide.
As a patch release, v0.13.6 maintains absolute backward compatibility with the storage format of the v0.13.x release line, allowing developers to drop in the update without needing to export and re-import their existing database files. How to Update to Kùzu v0.13.6
Integrated full-text search updates and wildcard pattern support into standard graph queries.
Fix: Roll back using your backup, then run kuzu dump on v0.135 to export raw data. Install v0.136 fresh and run kuzu load from the dump. This circumvents any on-disk format quirks.