aboutsummaryrefslogtreecommitdiffstats
path: root/scripts/release
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 17:48:47 +0000
committertv <tv@krebsco.de>2026-11-19 19:26:03 +0100
commitb95ba948a6e5ac04a75cd4d28ee3ac966dcc72bb (patch)
tree54671c4b846511f7601a903b8603ad5e2b4b9909 /scripts/release
parent59e889254b1fda2dcc8e3e6d596635d1b77f589f (diff)
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.
Diffstat (limited to 'scripts/release')
-rwxr-xr-xscripts/release7
1 files changed, 5 insertions, 2 deletions
diff --git a/scripts/release b/scripts/release
index 296766e..62a896a 100755
--- a/scripts/release
+++ b/scripts/release
@@ -12,8 +12,9 @@
# example too; then `cargo quick`, `cargo sim` and scripts/federation-check pass.
# 3. This build's `continuum --version` and the last release's (built in
# CONTINUUM_RELEASE_TARGET, ~/.cache/continuum/release unless set) say how one upgrades:
-# node by node where their wire versions meet and their Automerge is the same, else
-# every node together, which takes a major release from 1.0.0 on.
+# node by node where their wire versions meet, else every node together, which takes
+# a major release from 1.0.0 on; scripts/wire-check runs a swarm of both and checks
+# they do as said.
# 4. CHANGELOG.md's Unreleased notes become VERSION's, under a line saying so; the
# commit `release VERSION` holds it all, tagged vVERSION, its message saying how to
# upgrade, what the build speaks and knows, and the notes. A release knowing a later
@@ -141,6 +142,8 @@ if [ -n "$last" ]; then
die "$why: from 1.0.0 on, that takes a major release, not $version"
fi
fi
+ say "scripts/wire-check $last"
+ scripts/wire-check "$last" >&2 || die "a swarm of $last and this release doesn't do as said"
else
upgrade="The first release made by this script."
automerge_line=""