Skip to content

chore(antd-rust): bump antd-client to 0.3.0 for antd 0.15.0 - #324

Merged
Nic-dorman merged 1 commit into
mainfrom
chore/antd-rust-0.3.0
Oct 14, 2026
Merged

Nic-dorman merged 1 commit into
mainfrom
chore/antd-rust-0.3.0

Conversation

@Nic-dorman

Copy link
Copy Markdown
Member

The SDK package bump that follows the antd 0.15.0 release. Only antd-rust's public API changed since the 0.2.0 packages, so it is the only package bumped.

This PR

antd-client (antd-rust) 0.2.0 → 0.3.0, a minor bump:

Docs and text:

  • The range method docs say they need antd >= 0.15.0.
  • The error for a daemon that ignores the range now ends "upgrade to antd 0.15.0 or later", the same text antd-go uses since chore(antd): bump version to 0.15.0 #323.
  • README:
    • dependency line antd-client = "0.3";
    • the compatibility note said "Tested against antd 0.12.x"; it now says ranges need antd 0.15.0 and the rest of the API works with 0.14.x;
    • "new in 0.3.0" markers on the range rows and the error row;
    • an "Upgrading from 0.2.x" note for the new variant.

Not bumped

Package Changes since its 0.2.0 release Why no new version
antd-py, antd_client (Dart), antd (Ruby) Regenerated gRPC stubs (#315) and regen scripts and READMEs (#318, #320) The stubs gain the offset/length request fields, but none of these clients calls them, so their public API is unchanged
@withautonomi/antd (JS), Autonomi.Antd (C#), autonomi/antd (PHP), antd-mcp None Nothing changed
antd-go Range API Already released as antd-go/v0.15.0 with the daemon tag

Publishing

antd-client has never been on crates.io. publish-rust.yml needs a CARGO_REGISTRY_TOKEN on the crates-io environment for the first publish, and no such secret exists at environment or repo level yet. So after this merges, a rust-v0.3.0 tag would fail at the publish step. Push the tag once the token is in place; after the first publish, trusted publishing can replace it.

Testing (Windows)

  • cargo fmt --check, cargo clippy --all-targets --all-features --locked -D warnings and cargo doc --locked --no-deps are clean.
  • cargo test --locked: 139 tests pass across the unit, integration and doc-test suites.
  • cargo publish --dry-run --locked packages and builds antd-client 0.3.0.
  • The range methods themselves passed the 4.5 GiB devnet acceptance on dev2 against an antd built from main before the release.

🤖 Generated with Claude Code

0.3.0 is the first version with the byte-range methods
(data_stream_range, data_stream_public_range on both clients) and
AntdError::RangeNotSatisfiable. The new variant breaks exhaustive
matches on AntdError, which is not #[non_exhaustive], hence a minor
bump.

- Cargo.toml and Cargo.lock: 0.2.0 -> 0.3.0.
- The range docs say they need antd >= 0.15.0, and the old-daemon error
  now reads "upgrade to antd 0.15.0 or later", matching antd-go.
- README: dependency line 0.3, compatibility note (ranges need antd
  0.15.0; the rest works with 0.14.x), "new in 0.3.0" markers, and an
  upgrade note for the new variant.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Nic-dorman
Nic-dorman merged commit 124de4e into main Oct 14, 2026
5 checks passed
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.

1 participant