Skip to content

chore(antd): bump version to 0.15.0 - #323

Merged
Nic-dorman merged 1 commit into
mainfrom
chore/bump-0.15.0
Oct 13, 2026
Merged

Nic-dorman merged 1 commit into
mainfrom
chore/bump-0.15.0

Conversation

@Nic-dorman

Copy link
Copy Markdown
Member

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-capacity flag are new.

This PR

  • antd/Cargo.toml and antd/Cargo.lock: 0.14.0 → 0.15.0. The lock is hand-edited; CI's --locked check validates it.
  • Byte-range support now names its version:
    • openapi.yaml's Range parameter says "Added in antd 0.15.0"; older daemons ignore it and answer 200.
    • 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 together with the daemon, which is why its docs change here. antd-rust's matching docs go in the SDK package bump PR, together with its 0.3.0 version.

What 0.15.0 ships (since v0.14.0)

Byte-range downloads (#313, #316):

  • REST: Range on GET /v1/data/public/{address}/stream and POST /v1/data/stream.
  • gRPC: offset and length on the stream RPCs.
  • Only the chunks that overlap the range are fetched. The responses are 206 with Content-Range, or 416 with bytes */size; gRPC OUT_OF_RANGE carries the size in an x-content-range trailer.
  • antd-go adds DataStreamRange and DataStreamPublicRange on 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):

  • The new flag is --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.
  • Peak RSS for a 4.5 GiB read fell from 4,654 MiB to 887 MiB.
  • Re-reading more than about 256 MiB of distinct chunks now fetches them again; raise the flag to keep more cached.

Other changes:

Testing

  • dev2, main at db42419 (this PR only adds the version and doc text on top of it):
    • antd built from main, plus the Go and Rust range checkers rebuilt against main's antd-go (grpc v1.83.1, x/net v0.60.0) and antd-rust.
    • The 4.5 GiB acceptance on a 25-node ant-node 0.22.0 devnet: all pass over REST and gRPC. The 38 ranges fetched the same number of chunks as the pre-merge run, and antd logged 0 errors or warnings.
  • Mainnet, read-only, on the build(antd): repin ant-core 0.12.0 (ant-cli-v0.3.10) #319 build (the same compiled antd): 24/24.
    • Canary files downloaded byte-identically on 0.14.0 and the new build.
    • Ranges on a 485 MB file matched archive.org.
  • Locally: cargo check --locked passes; for antd-go, go vet, go test and gofmt pass.

After merge

  1. Push an annotated tag v0.15.0 at the merge commit. release.yml builds and signs; the stable tag requires signing, and the DigiCert certificate expires 2026-10-17.
  2. The auto-tag workflow cuts antd-go/v0.15.0.
  3. Add the cache-default and Go 1.26 notes above to the generated release notes.
  4. Then do the SDK package bump PR (antd-rust 0.3.0 and the others).

🤖 Generated with Claude Code

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>
@Nic-dorman
Nic-dorman merged commit fb857ae into main Oct 13, 2026
9 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