Kuzu V0 136 Fixed ((link)) Jun 2026

Embedded (in-process) like DuckDB, requiring no server setup.

kuzu --version # If output shows "0.136" without a build hash, you are affected.

Updating to the latest patch version depends on the environment and language binding you are using. To update the Python package via pip: pip install kuzu==0.13.6 --upgrade Use code with caution. To update the Node.js client library: npm install kuzu@0.13.6 Use code with caution.

Internal discussions also suggest that v0.136 fixed will serve as the foundation for the scheduled for Q1 next year. The team is now focused on fuzz testing and formal verification of the concurrency layer. kuzu v0 136 fixed

Kuzu, the blazing-fast, embedded property graph database, has recently undergone a major transition. Following the in late 2025, the original open-source repository was archived on GitHub . However, the community and a new successor project, LadybugDB , have continued to address critical bugs and performance bottlenecks identified in the v0.11.x and early v0.13 pre-releases. Key Fixes and Improvements in Recent Releases

Update your Cargo.toml dependency to point to the latest patch: [dependencies] kuzu = "0.13.6" Use code with caution. Looking Ahead

import kuzu # Initialize a database on disk db = kuzu.Database('./my_graph_db') conn = kuzu.Connection(db) # Create a schema and insert data conn.execute("CREATE NODE TABLE User(name STRING, age INT64, PRIMARY KEY (name))") conn.execute("CREATE (u:User name: 'Alice', age: 30)") # Execute a query safely using the patched v0.13.6 engine result = conn.execute("MATCH (u:User) RETURN u.name, u.age") while result.has_next(): print(result.get_next()) Use code with caution. Conclusion Embedded (in-process) like DuckDB, requiring no server setup

The refinements to the vectorized engine mean faster query results.

: Ownership of Transactions was moved from TransactionContext to TransactionManager to improve resource handling and prevent potential race conditions.

The release is not just a patch; it is a re-foundation. The three critical memory and concurrency bugs have been eradicated, performance has exceeded pre-regression levels, and the upgrade path is smooth for the vast majority of users. For any team currently stuck on v0.134 or suffering through v0.135, this update is mandatory. To update the Python package via pip: pip install kuzu==0

Are you facing a in your current graph project?

The v0.13.6 release is a targeted patch designed to harden the system against runtime crashes, incorrect query evaluations, and memory leak vulnerabilities. Below is a breakdown of the most significant fixes introduced in this version. 1. Memory Management and Leak Fixes

#if defined(__aarch64__) #define KUZU_ALIGNMENT 16 #else #define KUZU_ALIGNMENT 8 #endif

, your request likely refers to recent critical fixes in the

The changelog highlights a new optimistic concurrency control mechanism using 64-bit atomic timestamps. The team also removed the problematic spinlock implementation in favor of a mutex pool. Internal stress tests (100 threads performing 10,000 writes each) now show zero conflicts and 99.999% write atomicity.