From c1bf987314774d135316d95480baeb6eb7e1dc70 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 13:48:39 +0000 Subject: release: --version says what decides which builds work together `continuum --version` and `continuum-party --version` say, after the release, the wire versions the build speaks, the federation and the revisions of it it knows (with the `federation` feature), and the Automerge version it makes documents with: continuum 1.0.0 wire versions 52 to 52 federation 1: the base revision, revision 1 (merge-events) automerge 0.12.0 `-V` says the release alone, as before; continuum-party had no version at all. The Automerge version is the one the crate itself reports (`document::engine_version`), so it follows Cargo.lock. --- src/config/mod.rs | 1 + 1 file changed, 1 insertion(+) (limited to 'src/config/mod.rs') diff --git a/src/config/mod.rs b/src/config/mod.rs index a1e6328..3b8d305 100644 --- a/src/config/mod.rs +++ b/src/config/mod.rs @@ -1876,6 +1876,7 @@ pub(super) const UNSET: &str = "unset"; fn command() -> Command { let command = Command::new("continuum") .version(env!("CARGO_PKG_VERSION")) + .long_version(crate::release::described()) .about("continuum: a replicated Automerge document over Mycelium, libp2p or Tor") .arg( Arg::new(PRINT_CONFIG) -- cgit v1.3.1