feat: four-part versions, and a published version is never used again

0.2.6.1 is a maintenance release of 0.2.6. The build refused four parts, update_canary.sh's automatic bump could not add one to "6.1", and neither publish script would have noticed a version being published twice — which is what happened to 0.2.6 this morning: it was rebuilt with the Presentations hardening and uploaded over the first 0.2.6, and a room that had installed the first can never be offered the second. One release library now holds the version pattern (three or four parts, no leading zeros, no .0 maintenance), orders by dpkg --compare-versions, refuses a version that has ever been published or is not newer than all of them, uploads with --ignore-existing and checks the server's checksum, writes a manifest only for a package the server holds, and reads the channel back over HTTPS afterwards. update_canary.sh takes the version explicitly; update_stable.sh refuses to go backwards. The classroom updater refuses a manifest whose version, package name or checksum is malformed, and refuses a download whose own control file is not the version the manifest promised, so a room can never loop on reinstalling and rebooting. tests/test-release-versions.sh: 87 checks against a stand-in server and real dpkg. The Trixie gate now also rehearses a stable room: 0.2.2 to an interim 0.2.6.1 upgraded with settings, channel and Presentations=false intact, and the installed updater answering correctly. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-09-23 18:19:37 -05:00
parent 6f2d169355
commit 690ef95aff
9 changed files with 1260 additions and 147 deletions
@@ -110,3 +110,89 @@ curl -fsSL -o c.deb https://updates.riverofglorymn.org/canary/latest.deb
 sha256sum c.deb
 curl -fsS https://updates.riverofglorymn.org/canary/manifest.json
 ```
+
+## Version numbers and releasing
+
+```
+0.2.6     a feature release
+0.2.6.1   the first maintenance release of 0.2.6
+0.2.6.2   the second
+0.2.7     the next feature release
+0.3.0     a larger milestone
+```
+
+Three parts for a feature release, four for a maintenance release of one.
+The leading zero stays until Classroom is feature-complete; 1.0.0 belongs
+to the wider Ekklesia platform's milestone. Nothing else is a version: no
+leading zeros (dpkg reads `0.2.06` as `0.2.6`), no `0.2.6.0`, no suffixes.
+The build, both publish scripts and every classroom's updater refuse
+anything else, from one pattern held to one list of cases by
+`tests/test-release-versions.sh`.
+
+Which of two versions is newer is always `dpkg --compare-versions`, never
+our own arithmetic, because dpkg is what installs them:
+`0.2.2 < 0.2.6 < 0.2.6.1 < 0.2.6.2 < 0.2.6.10 < 0.2.7`.
+
+### A published version is never used again
+
+0.2.6 was rebuilt with later fixes and uploaded a second time under the
+same number, replacing the first upload. A room that had installed the
+first one could never be offered the second: the updater only installs a
+version newer than its own. So now:
+
+* `update_canary.sh VERSION` refuses a version that has ever been
+  published — on the server or in `repo/packages` — and one that is not
+  newer than every package ever published. It checks before building and
+  again after the Trixie gate.
+* Packages are uploaded with `rsync --ignore-existing`, and the checksum on
+  the server is compared with the one built before anything points at it.
+* A manifest is only written once the server holds exactly the package
+  and checksum it names.
+* After publishing, the channel is read back over HTTPS the way a classroom
+  reads it: manifest, versioned package, `latest.deb` and the version dpkg
+  reads out of the file must all agree.
+
+A publish that fails after the local copy into `repo/packages` has spent
+that number. Use the next one.
+
+### Canary
+
+```
+./update_canary.sh 0.2.6.1        # a maintenance release
+./update_canary.sh 0.2.7          # the next feature release
+```
+
+The version is always given. With four parts there are two possible next
+numbers, and which one a release is depends on what is in it. Run with no
+argument it prints the current canary and both candidates, and builds
+nothing.
+
+### Stable
+
+```
+./update_stable.sh 0.2.6.1
+```
+
+Only with the owner's written approval for that release. Stable is never
+given a package of its own: it is pointed at one canary already published,
+byte for byte, and refuses a version that is not newer than stable's
+current one or whose package the server does not hold with the same
+checksum.
+
+### Checking a channel without changing it
+
+```
+ROOT=$PWD bash -c 'source tools/release-lib.sh; release_verify_channel stable; release_verify_channel canary'
+```
+
+### Rehearsing an upgrade
+
+`tools/validate-trixie-release.sh NEW.deb [PREVIOUS.deb]` installs into a
+clean Debian 13 container. `VALIDATION_CHANNEL=stable` rehearses a stable
+room, for example the desktops' real path:
+
+```
+VALIDATION_CHANNEL=stable tools/validate-trixie-release.sh \
+    dist/ekklesia-classroom_0.2.6.1_amd64.deb \
+    repo/packages/ekklesia-classroom_0.2.2_amd64.deb
+```