aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--CHANGELOG.md4
-rw-r--r--Cargo.toml5
-rw-r--r--docs/operations.md3
3 files changed, 10 insertions, 2 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index da25cf3..db1aad2 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,10 @@ it from the release before ([`docs/operations.md`](docs/operations.md),
## Unreleased
+* Automerge is pinned to exactly the version `Cargo.toml` names, so no rebuild changes
+ what nodes must agree on unnoticed ([`docs/operations.md`](docs/operations.md),
+ [Upgrading](docs/operations.md#upgrading); [`Cargo.toml`](Cargo.toml)).
+
* `continuum-party show` says what a proposal does, in words, before a vote: who voted
what, the parties let in or taken out, keys by fingerprint, rules added and dropped, a
checkpoint and what moving there refuses, a revision, who writes where after it.
diff --git a/Cargo.toml b/Cargo.toml
index 3d359b5..04fe4e2 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -50,7 +50,10 @@ safelog = { version = "0.10", optional = true }
argon2 = { version = "0.6", features = ["getrandom"] }
async-stream = "0.3"
async-trait = "0.1"
-automerge = "0.12"
+# Exactly this one: nodes build remakes' snapshots and the founding changes byte for byte,
+# as Automerge encodes them, and a federation's events are kept in its changes; a change
+# of version is a change of what nodes must agree on (docs/operations.md, Upgrading).
+automerge = "=0.12.0"
axum = "0.8"
console-subscriber = { version = "0.5.0", optional = true }
base64 = "0.23"
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