Repository navigation
chore(antd): bump version to 0.15.0 - #323
Merged
Merged
Conversation
antd/Cargo.toml and Cargo.lock 0.14.0 -> 0.15.0. Minor: byte-range downloads (REST Range on both stream routes, gRPC offset/length) and the --chunk-cache-capacity flag are new. Byte-range support now names its version: openapi.yaml's Range parameter says "Added in antd 0.15.0", and antd-go's DataStreamRange docs (REST and gRPC) say "Requires antd >= 0.15.0". The error for a daemon that ignores the range now says "upgrade to antd 0.15.0 or later". antd-go is tagged with the daemon, so its docs change here; antd-rust's follow in the SDK package bump. 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.
Bumps antd from 0.14.0 to 0.15.0, the release Indelible is waiting on for antd-go's range API. It's a minor bump because byte-range downloads and the
--chunk-cache-capacityflag are new.This PR
antd/Cargo.tomlandantd/Cargo.lock: 0.14.0 → 0.15.0. The lock is hand-edited; CI's--lockedcheck validates it.openapi.yaml'sRangeparameter says "Added in antd 0.15.0"; older daemons ignore it and answer 200.DataStreamRangedocs (REST and gRPC) say "Requires antd >= 0.15.0".What 0.15.0 ships (since v0.14.0)
Byte-range downloads (#313, #316):
RangeonGET /v1/data/public/{address}/streamandPOST /v1/data/stream.offsetandlengthon the stream RPCs.Content-Range, or 416 withbytes */size; gRPCOUT_OF_RANGEcarries the size in anx-content-rangetrailer.DataStreamRangeandDataStreamPublicRangeon both clients. antd-rust has the same (feat(antd-rust): byte-range stream methods on the REST and gRPC clients #317), published separately.Chunk cache cap, a behaviour change (#314):
--chunk-cache-capacity/ANTD_CHUNK_CACHE_CAPACITY. Its default of 64 entries is about 256 MiB; before this, antd used ant-core's default of 1024, about 4 GiB.Other changes:
ant-cli-v0.3.10) with ant-protocol 4.0.0 (build(antd): repin ant-core 0.12.0 (ant-cli-v0.3.10) #319). antd's own source is unchanged.go 1.26.0when they upgrade.Testing
db42419(this PR only adds the version and doc text on top of it):cargo check --lockedpasses; for antd-go,go vet,go testand gofmt pass.After merge
v0.15.0at the merge commit.release.ymlbuilds and signs; the stable tag requires signing, and the DigiCert certificate expires 2026-10-17.antd-go/v0.15.0.🤖 Generated with Claude Code