Kuzu V0 136 Fixed [exclusive] Jun 2026

Kùzu enforces a strong schema by treating node labels and relationship types as explicit, underlying physical tables. Properties are stored in fixed-size blocks using advanced columnar compression techniques to maximize sequential memory access.

[Unstructured Data] ──> [BAML/LLM Extraction] ──> [Kùzu v0.13.6 Vector Index] ──> [Graph RAG Prompt] Vector Search Upgrades

In October 2025, Kùzu Inc. announced that it was "working on something new" and officially the Kùzu repository. While the core team is no longer actively supporting the project, the code remains open-source under the MIT License . What this means for you: kuzu v0 136 fixed

The finalizeCheckpoint improvement is crucial for long-running, disk-based graph storage, preventing unnecessary bloat.

The rapid evolution of graph database technology continues with the latest release of , the open-source, extremely fast, and embeddable graph database management system. While minor version increments might often seem like routine maintenance, Kùzu v0.1.3.6 is a critical update that addresses specific edge cases and performance bottlenecks reported by the community. Kùzu enforces a strong schema by treating node

Even with a “fixed” release, a small number of edge cases persist. If you encounter problems after upgrading to , try these solutions:

Fixed specific "wheel" build issues for Windows users, ensuring a smoother pip install kuzu experience. Type Safety: announced that it was "working on something new"

However, the open-source community has stepped in. The MIT-licensed source code is being actively carried forward under a new name: . For FreeBSD users, for example, the databases/kuzu port is being updated to Ladybug. If you are starting a new project, it is highly recommended that you search for "Ladybug database" to ensure you are building on the actively maintained version of the software.

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

We’ve rolled out a targeted update to improve the stability of our embedded property graph database