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 /Cargo.toml | |
| 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 'Cargo.toml')
| -rw-r--r-- | Cargo.toml | 5 |
1 files changed, 4 insertions, 1 deletions
@@ -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" |
