release: 0.6.0 — openCypher TCK 91.5%→97.7% (+239)#93
Merged
Conversation
added 2 commits
June 3, 2026 21:00
Bump python/rust binding versions to 0.6.0, add CHANGELOG [0.6.0] entry summarizing the conformance work since 0.5.0 (pattern/path matching, temporal, quantifiers, WITH/ORDER BY/aggregation, existential subqueries, validation), and document current openCypher TCK coverage in the README (97.7% overall; expressions 98.0%, clauses 97.2%, use cases 100%).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release prep for 0.6.0
A large openCypher conformance release. TCK pass rate moves from 91.5% (3549 executable) to 97.7% (3788 / 3876), +239 scenarios, zero regressions. 944/944 unit tests; functional clean.
Changes
0.6.0— Python (__init__.py) and Rust (Cargo.toml+Cargo.lock) bindings.[0.6.0]entry summarizing the work since 0.5.0 (pattern & path matching completeness, temporal cluster, quantifiers, WITH/ORDER BY/aggregation, existential subqueries, validation, multi-row write paths).Coverage by area
Release step (after merge, with your go-ahead)
Pushing the
v0.6.0tag triggers.github/workflows/release.yml, which publishes to PyPI and crates.io and creates the GitHub release. That step is intentionally left for explicit confirmation — not done in this PR.Windows CI (
test_*_timestamp*) is a known flake and is allowed to fail.