Kuzu V0 136 Fixed -

Simultaneous write operations risked race conditions when updating the local hash index during high-throughput ingest operations.

Full changelog in their GitHub releases.

All users on earlier v0.136 are strongly advised to upgrade. No changes to the public API or on-disk format – drop-in replacement.

Prepared statements are now explicitly cached within the client context.

Fixed issues where the system would attempt to recover twice from a corrupted WAL. Query Processor Stability: kuzu v0 136 fixed

Shortly after the release of this codebase, Kuzu Inc. announced they would no longer actively maintain the project under its original commercial umbrella. However, because the technology is licensed under the permissive , the community quickly rallied to preserve its advanced vectorized join algorithms.

If you've encountered the term in developer forums or release notes, you're likely looking at the latest iteration of the django-components library. A crucial evolution has arrived: django-components version 0.136 . In the world of modern web development, django-components has carved out a niche for itself. Inspired by the component-based architectures of frameworks like React and Vue, it allows developers to encapsulate Django templates, CSS, and JavaScript into reusable "components," bridging the gap between backend simplicity and frontend modularity.

v0.1.36 introduced the REFERENCES keyword, allowing users to define explicit foreign keys.

Run:

Improved stability when running Kùzu within Docker containers or on smaller cloud instances. Why You Should Update to the Latest Kùzu Release

The parser has been hardened to handle more complex query plans. Specifically, bugs related to how the query optimizer handled certain types of joins in multi-hop queries have been resolved, leading to more predictable execution paths. 3. Concurrency and Thread Safety As an embeddable database, thread safety is paramount.

In summary, Kuzu v0.1.3.6 is a critical maintenance release. It might not introduce a long list of flashy new features, but its focus on "fixed" components makes it the most stable version of the v0.1 branch to date. For anyone currently running a Kuzu-backed application, upgrading to v0.1.3.6 is highly recommended to benefit from the improved query accuracy and system stability.

: Existing versions (like v0.11.3 ) remain fully functional for local development and embedded use cases. No changes to the public API or on-disk

The project was led by Kenji, a meticulous and passionate developer with a vision for Kuzu to become a household name in the tech community. His team was a diverse group of young talent, each bringing their unique skills and perspectives to the table.

acted_in.csv: src_id,dst_id,role p1,m1,Lead

While v0.136 doesn't exist, the actual v0.11.x releases contain a wealth of significant fixes. This section provides the most exhaustive breakdown of those improvements, focusing on enhancing stability, performance, and data integrity. All fixes are part of the v0.11.2 and v0.11.3 releases.

Specific to multi-threaded queries involving path-finding (e.g., variable-length relationships), v0.1.36 optimized memory buffer reuse. This fixed out-of-memory (OOM) errors encountered when running breadth-first searches over dense graphs with high cardinality. Query Processor Stability: Shortly after the release of