revert: drop the settlement-version quote gate from this train (#23) - #24
Merged
Conversation
Reverts the merge of #23. The change is held off the 2026-08-18 release train and will land with its coordinated set. #23's own body states "Release readiness: coordinated set, do not merge alone" and that it "should not land until the coordinated set is fleet ready", naming ant-node #204 and ant-client #171 as carrying the open gates. Both are still open with changes requested, so the enforcement and adversarial evidence for this T3 change set — and its ADR — exist only on unmerged branches. Nothing here changes behaviour on its own: the new variants are never constructed unless a client sends them and a node acts on them, both of which are separate PRs. This revert is therefore inert on the wire, and restores ant-protocol to exactly the released v2.3.2 tree. Re-land as a set once #204 and #171 are ready. Note that ADR-0010 is now taken on ant-node by the beta upgrade channel ADR, so the settlement ADR needs renumbering before #204 lands. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
7 tasks
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.
Reverts the merge of #23, holding the settlement-version change off the
2026-08-18 release train. It re-lands with its coordinated set.
Why
#23's own body carries a "Release readiness: coordinated set, do not merge alone" section:
The coordinated set it names — ant-node #204 and ant-client #171 — are both still
OPENwithchanges requested. That leaves this train shipping the wire vocabulary while the enforcement and
adversarial evidence for a T3 change set, and its ADR, exist only on unmerged branches.
Blast radius: none
By #23's own analysis the change is inert on the wire — the new variants are never constructed
unless a client sends them and a node acts on them, and both are separate PRs. The revert restores
mainto exactly the releasedv2.3.2tree:ant-protocol therefore stays at 2.3.2 and drops off this train entirely.
Re-landing
Land as a set once #204 and #171 are ready. One thing to fix first: ADR-0010 is now taken on
ant-node by
ADR-0010-beta-upgrade-channel-semantics.md(landed with ant-node #208), so thesettlement ADR needs renumbering.
Worth considering a mechanism that actually holds a PR like this — draft state, a blocking label,
or a Linear
blocksrelation — since a release-readiness condition written in the PR body does notstop a merge.
🤖 Generated with Claude Code