[prrao87]

Why

Release the changes merged since 0.3.1 to crates.io and PyPI. The version is 0.4.0 rather than 0.3.2 because #70 is a breaking change for Rust users, and before 1.0 a breaking change takes a minor bump.

What changed

• The version moves from 0.3.1 to 0.4.0 in the four crate manifests, python/pyproject.toml and .bumpversion.toml (bump-my-version bump minor).
• The version also moves in the three lockfiles that carry it, which bump-my-version doesn't update: the root Cargo.lock, the Python bindings' own Cargo.lock, and python/uv.lock. Only the workspace packages' version lines change; no dependency moves.

What 0.4.0 contains

Breaking (Rust):

• refactor(config)!: make graph config mappings private #70: GraphConfig's node and relationship mappings are private. Code that wrote to them directly must use GraphConfigBuilder. A deserialized config is now validated like a built one, so a saved config with an unnormalized key, or a relationship whose endpoint label has no node mapping, fails to load. The Python API is unaffected.

Query results that change:

• fix(planner): bind each relationship once per match #82: within one MATCH, two single-hop relationships of the same type no longer bind the same edge, so some queries return fewer rows (openCypher relationship uniqueness).
• fix(planner): match a reused relationship variable as the same edge #83: a relationship variable written again, as in (a)-[r:KNOWS]->(b), (c)-[r]->(d), matches that same relationship. It used to return wrong rows or fail to plan. Reusing one in a variable-length segment now raises an error within one MATCH.

Python:

• refactor(python): wrap the compiled classes in typed, documented python classes #71: the public classes are typed, documented Python classes wrapping the compiled ones. Names, signatures and behaviour are unchanged. ExecutionStrategy, SqlDialect and DistanceMetric are IntEnums with the same members and values, and passing the wrong class raises TypeError naming the parameter. The API reference is generated from the docstrings.

Fixes: #65 (distinct counts on empty input), #66 (physical column casing in graph scans), #67 (one trailing semicolon accepted).

Docs: #63, #64, #68, #69.

Validation

• cargo test --workspace, cargo clippy --workspace --all-targets -- -D warnings: pass.
• make test in python/: 1619 passed; the rebuilt package reports version 0.4.0. make lint: clean.
• cargo publish --dry-run -p lance-csr-catalog -p lance-csr: both crates package and build from their packaged sources (11 and 71 files; no internal files), and the uploads are skipped.
• Benchmarks: no code changes here. fix(planner): bind each relationship once per match #82 and fix(planner): match a reused relationship variable as the same edge #83 were benchmarked against main in fix(planner): bind each relationship once per match #82.

Release steps after merge

1. Run python-publish.yml with mode=dry_run on main. It's the only place the release wheels are built and tested.
2. Publish the crates by hand, lance-csr-catalog first, then lance-csr.
3. Publish a GitHub release tagged v0.4.0 from main. That runs python-publish.yml, which publishes to PyPI once its builds and tests pass.

🤖 Generated with Claude Code

[cloudflare-workers-and-pages]

Deploying lance-csr with    Cloudflare Pages

Latest commit:	dbbb236
Status:	✅  Deploy successful!
Preview URL:	https://17ea414d.lance-csr.pages.dev
Branch Preview URL:	https://chore-bump-0-4-0.lance-csr.pages.dev

View logs