From b95ba948a6e5ac04a75cd4d28ee3ac966dcc72bb Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 17:48:47 +0000 Subject: scripts/wire-check: a swarm of the last release and this tree Four nodes on this host over libp2p on loopback, two of a release tag's build and two of this tree's, in turns, each seeded with the one before. Where the two builds' wire versions meet, each node writes, and the check is that every node reads what each wrote and that none logs a peer of another wire version. Where they don't, that the tag's nodes log this tree's as such, so their operators know to upgrade. scripts/release runs it against the last release, after saying from the two builds' --version how the release upgrades: so a release that says it rolls out node by node has been seen to. docs/development.md says how a change to the wire format is made: a new version beside the ones spoken already, the older kept frozen. --- docs/development.md | 18 +++++++++++++++++- 1 file changed, 17 insertions(+), 1 deletion(-) (limited to 'docs/development.md') diff --git a/docs/development.md b/docs/development.md index 39eabdf..f921d22 100644 --- a/docs/development.md +++ b/docs/development.md @@ -123,7 +123,8 @@ and compares what the two say they are (`continuum --version`): * **wire versions**: where they share one, the release rolls out node by node; where they don't, every node upgrades together, which from 1.0.0 on only a major release - may ask; + may ask. `scripts/wire-check` checks it, by a swarm of the last release's nodes and + this tree's (below); * **Automerge**: where it differs, nobody remakes until every node runs the release; * **the federation's revisions**: a release knowing a later one than the last is tagged `federation-.` too, so that later releases are checked against it. @@ -131,3 +132,18 @@ and compares what the two say they are (`continuum --version`): What it finds heads the release's notes in the change log and its tag's message, with what the build speaks and knows, and the notes. Before 1.0.0 every upgrade may still be taken as a flag day, but the notes say when it isn't. + +`scripts/wire-check [TAG]` (the last release unless given) runs four nodes on this host, +over libp2p on loopback: two of the tag's build and two of this tree's, in turns. Where +their wire versions meet, each writes, and it checks that every node reads what each +wrote and that none logs a peer of another wire version; where they don't, that the +tag's nodes log this tree's as such, so their operators know to upgrade. + +```sh +scripts/wire-check v0.0.1 +``` + +A change to the wire format is a new version (`wire::VERSION`) beside the ones the build +speaks already: the messages of the version before keep their types, frozen, and are +encoded and decoded in `transport/wire.rs` beside the newest's, and `golden_bytes` keeps +the bytes of each. A later release raises `wire::OLDEST` to leave the oldest out. -- cgit v1.3.1