chore(ffi): bump ant-core to 0.8.1 — ship the re-bootstrap recovery; AntFfi 0.0.9 - #247
Merged
Merged
Conversation
…tstrap recovery; AntFfi 0.0.9 The FFI crate (compiled into the Python/Swift/Kotlin SDK artifacts) was still on ant-core 0.6.0, which predates the saorsa-core runtime re-bootstrap recovery (V2-1036): a shipped client could starve its routing table and never heal without a process restart. ant-core 0.8.1 is the release cut for exactly that uplift — ant-protocol 2.3.5 floors saorsa-core at 0.27.3, so the lock resolves the fix natively (no hand pin). The direct ant-protocol pin moves 2.3.2 -> 2.3.5 in lockstep per the graph-skew rule, realigning ffi with antd on the 0.8.x core line. AntFfi version 0.0.9 (crate + pyproject together — the release version invariant requires wheel metadata == ant_ffi_version() == tag, so the first PyPI release becomes python-v0.0.9). ant-ffi: 16/16 tests, fmt + clippy -D warnings clean against the new graph. No source changes required. Co-Authored-By: Claude Fable 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
1 participant
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.
Why now
The FFI crate — the library compiled into the Python wheels (and the Swift/Kotlin artifacts) — still pinned ant-core 0.6.0 (
ant-cli-v0.3.3), which predates the saorsa-core runtime re-bootstrap recovery (WithAutonomi/saorsa-core#153, V2-1036). A shipped client could starve its routing table and never heal without a restart — the defect the rest of the stack just fixed (antd in #241).ant-cli-v0.3.6/ ant-core 0.8.1 is the release cut for exactly that uplift, so the first public PyPI release should carry it rather than ship the known bug.Changes
ffi/rust: ant-coreant-cli-v0.3.3→ant-cli-v0.3.6(0.6.0 → 0.8.1); directant-protocolpin 2.3.2 → 2.3.5 in lockstep (graph-skew rule). Lock now resolves saorsa-core 0.27.3 natively — ant-protocol 2.3.5 floors it, no hand-pin needed (unlike antd on 0.8.0).ffi/python/pyproject.tomltogether): the release version invariant enforces wheel metadata ==ant_ffi_version()== tag, so the PyPI release tag becomespython-v0.0.9.Verification
cargo fmt --check, clippy-D warnings— all clean against the new graph, zero source changes required (matches antd's experience on the 0.6.0 → 0.8.0 jump).publish=testpypidispatch (re-proves the four-leg matrix and the 0.0.9 version invariant) → tagpython-v0.0.9. TestPyPI already carries 0.0.8 from yesterday's validated dry run.Follow-up (not this PR)
antd could move 0.8.0 → 0.8.1 too, so its saorsa-core 0.27.3 floor lives in the manifest instead of only the hand-pinned lock.
🤖 Generated with Claude Code