Skip to content

release: prepare v4.0.0 - #93

Merged
krinart merged 2 commits into
trunkfrom
release/v4.0.0
Aug 20, 2026
Merged

release: prepare v4.0.0#93
krinart merged 2 commits into
trunkfrom
release/v4.0.0

Conversation

@krinart

@krinart krinart commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Bumps Cargo.toml to 4.0.0 and adds docs/release_notes/v4.0.0.md covering everything unreleased since 3.0.0 (the last version actually published to crates.io): the breaking query()/query_with_bindings() async change, parameterized queries, dataset refresh, mTLS, Nsql/NsqlGenerateSQL, Search, active-query management, and runtime status.
  • Targets 4.0.0 rather than 3.1.0/3.2.0 for two reasons: query() becoming async is a breaking change, and 3.1.0/3.2.0 were never actually published (see note below) — 4.0.0 is the true next version after 3.0.0.

Versioning note

v3.1.0's crates-publish run failed its own version-consistency check, because that commit's Cargo.toml had already been bumped to 3.2.0 by an unrelated dependency-upgrade PR (#66) merged into the same release. v3.2.0 was tagged as a GitHub Release but left in draft and never published either. crates.io's newest_version is still 3.0.0. Flagging this explicitly so whoever cuts the release is aware — happy to adjust the target version if there's a reason to prefer something else.

Test plan

  • cargo build, cargo test --lib (235 passed), cargo fmt --check all clean locally.
  • cargo test --tests — everything passes except 5 pre-existing client_test.rs cases that need a live local spiced with a taxi_trips dataset (which CI's build.yml provisions); not exercised in this environment, unrelated to this change.

Bumps Cargo.toml to 4.0.0 and adds release notes covering everything
unreleased since the last version actually published to crates.io
(3.0.0): the breaking query()/query_with_bindings() async change,
parameterized queries, dataset refresh, mTLS, Nsql/NsqlGenerateSQL,
Search, active-query management, and runtime status.

v3.1.0 and v3.2.0 were never published — v3.1.0's crates-publish run
was rejected by the workflow's version-consistency check (that
commit's Cargo.toml had already been bumped to 3.2.0 by an unrelated
PR), and v3.2.0 was left in draft. This targets 4.0.0 both for the
breaking change and because it is the true successor to 3.0.0.
@krinart krinart self-assigned this Aug 19, 2026
@krinart
krinart enabled auto-merge (squash) August 19, 2026 23:15
@krinart
krinart disabled auto-merge August 20, 2026 00:26
Removed outdated versioning notes and example code from release notes.
@krinart
krinart merged commit a2aebba into trunk Aug 20, 2026
16 of 17 checks passed
@krinart
krinart deleted the release/v4.0.0 branch August 20, 2026 01:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants