github getzep/graphiti v0.30.0
v0.30.1 - Neo4j Custom Database Fix, Search Fixes and Other Miscellaneous Fixes

latest releases: mcp-v1.1.0, v1.1.0
6 hours ago

Fixed: Neo4j queries now respect the configured database
Neo4jDriver.execute_query() previously ignored the driver's database setting and ran all queries (including searches) against the server's home database, while session-based writes used the configured one (#1481, #851, #798). Queries are now correctly routed to the configured database, defaulting to neo4j. A per-call override is also supported via execute_query(..., database_="name").

⚠️ Behavior change for existing deployments:

WHO IS AFFECTED: This only impacts self-hosted Neo4j Enterprise deployments (multi-database support is an Enterprise feature) where the database parameter was manually set to something other than neo4j in the Graphiti client, or where the server's default database was renamed. If you run a standard Neo4j setup with the default neo4j database, no action is needed.

If your server's home database is not named neo4j and you don't pass database to the driver, queries now target neo4j instead of your home database — pass your database name explicitly to keep the old behavior.
If you configured a custom database, reads now correctly target it. Data previously written via execute_query may reside in your home database and may need to be migrated.

What's Changed

New Contributors

Full Changelog: v0.29.3...v0.30.0

Don't miss a new graphiti release

NewReleases is sending notifications on new releases.