Internal hooks for tracking node and relationship properties during high-concurrency writes have been refined to prevent dangling pointers. 2. Cypher Query Planner Corrections
Fixed specific "wheel" build issues for Windows users, ensuring a smoother pip install kuzu experience. Type Safety:
The release of django-components is a clear signal of the library's evolution. While the removal of built-in validation is a breaking change that requires developer action, it is a change made in the interest of a more sustainable and flexible architecture.
A European fintech company using Kuzu to trace transaction rings across 500,000 accounts had to roll back to v0.135 after experiencing nightly crashes. After applying , they reported: kuzu v0 136 fixed
The v0.136 release is essential for developers seeking stability, particularly those working across different operating systems. While it introduces a notable breaking change, it also resolves several key bugs that could cause unexpected behavior and errors.
Previously, from versions 0.96 up to 0.135 , the library had built-in input validation. This allowed developers to define the expected data types and requirements for a component's inputs, and the system would automatically raise errors for invalid data.
Traditional graph databases rely heavily on heavy client-server architectures. This introduces substantial network latency and infrastructure overhead. Kùzu mirrors the lightweight, serverless design patterns pioneered by DuckDB but tailors its engine specifically for graph analytics. Internal hooks for tracking node and relationship properties
Embedded (in-process) like DuckDB, requiring no server setup.
Shortly after the release of these critical stability fixes, Kùzu Inc. was acqui-hired, and the original Kùzu GitHub repository was placed into permanent read-only archival mode. Despite the lack of new mainline feature development, v0.13.6 remains a production-ready milestone for local graph processing. Releases · kuzudb/kuzu - GitHub
v0.13.6 hardens the DROP_VECTOR_INDEX lifecycle routines. It completely purges cached properties from the execution buffer, reclaiming 100% of temporary execution memory immediately after an index drop command completes. 3. Parallel Execution Under High Core Counts Type Safety: The release of django-components is a
Version 0.136 was a feature release aimed at improving:
| Metric | Kuzu v0.135 (unstable) | Kuzu v0.136 (fixed) | Improvement | | --- | --- | --- | --- | | Average query latency | 340 ms | 212 ms | | | Memory usage (peak) | 5.2 GB | 1.8 GB | 65% reduction | | Multi-threaded throughput | 1,200 ops/sec | 2,450 ops/sec | 104% increase | | Crash rate (24 hours) | 1 crash per 6 hours | 0 crashes | 100% stable |
For developers running Kùzu in production or utilizing it inside local data science pipelines, upgrading to v0.13.6 provides several immediate operational advantages:
Embedded databases must maintain a strict memory footprint, as they share the host application's memory space. Kùzu v0.13.6 resolves specific edge-case memory leaks that occurred during complex graph traversals and recursive join operations.
If an explicit transaction encountered a failure during bulk data insertions and immediately executed a rollback, internal page tracking headers could fall out of sync with the physical disk storage.