Kuzu V0 136 Fixed Jun 2026

Graph databases often suffer from massive performance penalties during complex multi-hop Cypher queries. Kuzu circumvents this through factorized query execution and vectorized processing. Version 0.13.6 introduces critical fixes to keep these pipelines error-free under rigorous enterprise execution.

| Category | Specific Fix in v0.11.2 / v0.11.3 | Benefit | | :--- | :--- | :--- | | | Fixed i128 minimum value check during parsing. | Ensures correct handling of very large integers, preventing silent data corruption. | | Delete Operations | Fixed a bug in DETACH DELETE on local relationship tables. | Guarantees that when you delete a node, all its connecting relationships are reliably removed, maintaining graph consistency. | | Indexing & Search | Implemented fts update functionality. | Enabled updates to a Full-Text Search index, making it dynamic and practical for real-world applications. | | Data Types & Structures | Implemented casting between union types and fixed nested unions/lists/arrays. | Provided greater flexibility and reliability for complex data manipulations within the graph. | | Query Execution | Fixed an issue in OnDiskGraph vertex scanning during transactions and fixed a flat select bug (from v0.7.1 ). | These fixes enhance transaction safety and ensure accurate results in specific query scenarios. | | Extension Management | Bundled four core extensions ( algo , fts , json , vector ) directly in v0.11.3 . | This eliminated the previous requirement for a local extension server, simplifying the setup process. | | Performance & Cleanup | Cleaned up unused memory estimation functions and fixed LSQB benchmark runs. | Reduced potential memory overhead and improved performance testing for developers. | | Build & Packaging | Improved static link extension error messages, enabled Rust static extensions, updated setuptools , and removed an uv dependency. | Streamlined the build process for developers integrating Kùzu, especially for those using Rust or packaging the database. |

For more in-depth, technical insights into the Kùzu roadmap, the official GitHub roadmap #4029 highlights features like mutable indices, which are a major focal point for continued improvements. Conclusion kuzu v0 136 fixed

This ensures that the robust core of Kùzu will continue to evolve and improve.

If you are looking for a graph database that brings speed, simplicity, and AI integration together, the latest version of Kùzu is a compelling choice. Stay Up to Date kuzudb/kuzu Documentation: kuzudb.github.io If you'd like, I can: | Category | Specific Fix in v0

pip install -U kuzu

Fixed phrase-matching regressions to maintain optimal string indexing speed. Python, Swift, Azure, & LLM integrations | Guarantees that when you delete a node,

🚀 Kuzu v0.136 is fixed! The patch resolves the recursive CTE memory leak and MATCH path timeouts from the initial release.

Have you tested Kuzu v0.136 fixed in your environment? Share your results in the comments below or contribute to the official Kuzu GitHub repository. Found another bug? The maintainers are prioritizing reports against this version above all others.

Here is the most effective, step-by-step approach to resolving code 136, ranked from easiest to most complex:

Addressed issues related to memory management during indexing and querying in concurrent environments.