Based on the syntax of your request, you are referring to Kuzu version 0.1.36 (KùzuDB), the open-source embeddable graph database.
Stability is the backbone of any database, and the latest patch for the Kùzu embedded graph database, version 0.13.6, is all about refinement. As Kùzu continues to gain traction for its blazing-fast, serverless integration into AI and analytical pipelines, this update ensures that the "wisdom" (as its Sumerian namesake suggests) remains unshakeable. What’s Under the Hood?
The kuzu v0.136 fixed 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.
by default, eliminating the need for manual installation of these tools. Cross-Platform Portability:
The kuzu v0.136 fixed release represents exactly what the open-source community does best: rapid identification, transparent communication, and surgical correction of a critical bug without waiting for a major release cycle.
What’s Fixed
- Crash / regression in [common scenario, e.g., “executing recursive joins” or “scanning large lists”].
- Memory leak when handling [relevant operation].
- Incorrect results for edge cases involving [e.g., “NULL values in indexed columns”].
Could you clarify where you saw the "v0.136" reference?It's possible it refers to: A specific commit hash (though usually longer).
As a high-performance, embedded graph database modeled after the simplicity of SQLite, Kuzu continues to be the go-to for localized, blazing-fast graph queries without the overhead of heavy external servers. 🛠️ What's New & Fixed Engine Stability
A quick heads-up for anyone tracking the Kuzu graph database releases:
The v0.136 issues (query hangs on certain MATCH patterns + memory leak in recursive joins) have been patched in the latest hotfix.