Repository navigation
chore(antd-rust): bump antd-client to 0.3.0 for antd 0.15.0 - #324
Merged
Merged
Conversation
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>
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
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.
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:
data_stream_rangeanddata_stream_public_rangeon bothClientandGrpcClient.AntdError::RangeNotSatisfiable.AntdErroris not#[non_exhaustive], so the new variant breaks amatchwithout a catch-all arm.Docs and text:
antd-client = "0.3";Not bumped
offset/lengthrequest fields, but none of these clients calls them, so their public API is unchangedantd-go/v0.15.0with the daemon tagPublishing
antd-client has never been on crates.io. publish-rust.yml needs a
CARGO_REGISTRY_TOKENon thecrates-ioenvironment for the first publish, and no such secret exists at environment or repo level yet. So after this merges, arust-v0.3.0tag 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 warningsandcargo doc --locked --no-depsare clean.cargo test --locked: 139 tests pass across the unit, integration and doc-test suites.cargo publish --dry-run --lockedpackages and builds antd-client 0.3.0.🤖 Generated with Claude Code