aboutsummaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 17:25:11 +0000
committertv <tv@krebsco.de>2026-11-19 19:25:49 +0100
commiteeec08b8d15ac3c3301060c71772a664bd2a4685 (patch)
treee464d3301a573095292b71f3664f4d9a6cac150f /docs
parent5f9469e11b09c03d58abafe1f0210b509228315c (diff)
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.
Diffstat (limited to 'docs')
-rw-r--r--docs/operations.md3
1 files changed, 2 insertions, 1 deletions
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