From eeec08b8d15ac3c3301060c71772a664bd2a4685 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 17:25:11 +0000 Subject: Cargo.toml: Automerge pinned to exactly 0.12.0 Nodes build remakes' snapshots and a federation's founding changes byte for byte, as Automerge encodes them: a build with another Automerge rejoins instead of switching, and could build another genesis change. `automerge = "0.12"` let `cargo update`, or a distribution building without the lock, take any 0.12.x. It names exactly 0.12.0 now, which the lock holds already, so that moving it is a change made on purpose, said in the change log. --- docs/operations.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/operations.md b/docs/operations.md index d100a49..0f906eb 100644 --- a/docs/operations.md +++ b/docs/operations.md @@ -142,7 +142,8 @@ A node upgrades by restarting with its files. What to know: * **Automerge.** A remake needs every node to build the same snapshot, byte for byte, so the same Automerge version everywhere; a node with another one rejoins instead of switching ([`remakes.md`](remakes.md), [Limits](remakes.md#limits)). Don't remake while - the swarm runs two versions. + the swarm runs two versions. A build has exactly the Automerge its `Cargo.toml` names + (`automerge` in `--version`), and a release changing it says so in the change log. * **The dashboard** reloads by itself once its node serves another version of it. ## Behind a reverse proxy -- cgit v1.3.1