Repository navigation
chore(release): bump the workspace to 4.2.0 - #297
Merged
Merged
Conversation
Workspace version and all 26 internal crate pins, uni-pydantic's own version and its `uni-db>=` floor, the root, fuzz and uv lockfiles, and the generated Python API page. Release notes cover the 53 commits since 4.1.1: rustic-ai#293/rustic-ai#294 (Locy FOLD identity and ungrouped YIELD), the OPTIONAL MATCH, relationship-uniqueness, reachability and WITH-rebind wrong answers, the chunked-scan L0 data loss, UNIQUE-key and FTS/vector staleness, Locy value types and fact dedup, `execution_batch_size`, and the W2-W6 harnesses that found them. Results change for `sum` of nothing (now 0), anonymous variable-length relationships (one row per path), Locy value types, strict Locy conditions and maps with an `_id` key. 4.2.0 also carries source-level Rust API changes (`UniConfig::execution_batch_size`, two `LocyCompileError` variants, `StorageManager::existing_row_count`, the `VlpOutputMode` split). The notes list them first.
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.
Bumps the workspace from 4.1.1 to 4.2.0 and adds the release notes for the 53 commits since 4.1.1, merged in #295.
What changes
Cargo.toml: the workspace version and all 26 internal crate pins.Cargo.lock,fuzz/Cargo.lockandbindings/uni-pydantic/uv.lockrefreshed. Only workspace-crate versions move.bindings/uni-pydantic/pyproject.toml: its own version and theuni-db>=floor.website/docs/reference/python-api-symbols.mdregenerated withscripts/gen_python_api_reference.py(--checkpasses).docs/release_notes/RELEASE_NOTES_4.2.0.md.Why a minor and not a patch
Some results change in 4.2.0:
sumof nothing is now 0, an anonymous variable-length relationship returns one row per path, Locy keeps value types and raises on a condition it cannot evaluate, and a map with an_idkey is no longer a node. It also addsexecution_batch_sizeandWHERE n:A|B.There are four source-level Rust API changes, listed first in the notes:
UniConfig::execution_batch_sizefield;LocyCompileErrorvariants;StorageManager::materialized_row_countrenamed toexisting_row_count;VlpOutputMode::EndpointsOnlysplit into two variants.Code that builds
UniConfigwith a full struct literal, or matchesLocyCompileErrorexhaustively, will need a small change.Tests run
cargo check -p uni-dbbuilds at 4.2.0.gen_python_api_reference.py --checkpasses.4.1.1references are left outside earlier release notes and compliance reports.No code changed in this PR. The changes being released were tested in #295.