GraphForge v0.3.8 is the milestone release: all 3,885 openCypher TCK scenarios passing.

For an embedded Python graph database, that is a big line to cross. It means the query engine is no longer being judged only by bespoke tests; it is being exercised against the community compatibility kit.

What Shipped

• 100% openCypher TCK compliance with zero failures and zero expected failures
• Nanosecond precision handling for temporal types
• Statement clock caching for consistent now()-style calls within a query
• Extreme year support and large duration handling
• IANA timezone name preservation
• Aggregate detection fixes in quantifier expressions
• OPTIONAL MATCH WHERE placement and coalesce type inference fixes
• O(n²) to O(1) graph statistics updates
• Parser fast path for long CREATE sequences

Why We're Excited

This release made correctness a headline feature. For graph tooling meant to sit inside analytical workflows, compatibility is not decoration. It is what lets users trust the engine with familiar Cypher semantics.

Source

• GitHub release: GraphForge v0.3.8