Skip to content

chore(ffi): bump ant-core 0.3.0 -> 0.3.1 (ant-cli-v0.2.11) - #208

Merged
Nic-dorman merged 1 commit into
mainfrom
chore/ffi-ant-core-0.3.1
Jul 9, 2026
Merged

Nic-dorman merged 1 commit into
mainfrom
chore/ffi-ant-core-0.3.1

Conversation

@Nic-dorman

Copy link
Copy Markdown
Member

Bumps the ffi's pinned ant-core from ant-cli-v0.2.10 (0.3.0) to ant-cli-v0.2.11 (0.3.1).

Why bump: 0.3.1 carries FFI-relevant fixes:

Graph safety: ant-core 0.3.1 keeps ant-protocol = "2.2.2" — identical to the ffi's existing pin — so no saorsa-core/evmlib graph skew. Also force-bumped quinn-proto in the ffi lockfile to 0.11.16 so the RUSTSEC patch actually ships in the FFI binary (it was resolving to 0.11.14 independently).

Checks: cargo build + cargo clippy -D warnings + cargo fmt --check + 8 unit tests all green.

Note: antd still pins ant-cli-v0.2.10 (0.3.0) on its own release lane; realign when antd next bumps. This feeds the next AntFfi mobile release (v0.0.5, alongside #207).

🤖 Generated with Claude Code

Picks up the data_download shrunk-DataMap resolve fix, a block_in_place
panic fix in data_download, and the quinn-proto RUSTSEC-2026-0185 security
bump. ant-core 0.3.1 keeps ant-protocol 2.2.2, so the dependency graph is
unchanged and the pin stays graph-safe. Also force-bumped quinn-proto in the
ffi lockfile to 0.11.16 so the RUSTSEC patch actually ships in the FFI binary.

build + clippy -D warnings + fmt + 8 tests green.

antd still pins ant-cli-v0.2.10 (0.3.0) on its own release lane; realign
when antd next bumps.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@Nic-dorman
Nic-dorman merged commit c86a240 into main Jul 9, 2026
1 check passed
@Nic-dorman
Nic-dorman deleted the chore/ffi-ant-core-0.3.1 branch August 6, 2026 08:26
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