diff options
| author | tv <tv@krebsco.de> | 2026-11-19 17:25:11 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 19:25:49 +0100 |
| commit | eeec08b8d15ac3c3301060c71772a664bd2a4685 (patch) | |
| tree | e464d3301a573095292b71f3664f4d9a6cac150f /CHANGELOG.md | |
| parent | 5f9469e11b09c03d58abafe1f0210b509228315c (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 'CHANGELOG.md')
| -rw-r--r-- | CHANGELOG.md | 4 |
1 files changed, 4 insertions, 0 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. |
