diff options
| author | tv <tv@krebsco.de> | 2026-11-19 13:48:39 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 14:53:44 +0100 |
| commit | c1bf987314774d135316d95480baeb6eb7e1dc70 (patch) | |
| tree | 6af5e2f654793d75a30c2f5afbae978e8d1f4fd8 /src/federation | |
| parent | 3b4d0cc4f167ca77d74110cb59c9c85276723965 (diff) | |
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.
Diffstat (limited to 'src/federation')
| -rw-r--r-- | src/federation/party.rs | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/src/federation/party.rs b/src/federation/party.rs index 2c8dc4b..d829cc9 100644 --- a/src/federation/party.rs +++ b/src/federation/party.rs @@ -81,6 +81,8 @@ fn default_node() -> String { fn command() -> Command { let id = |name: &'static str| Arg::new(name).required(true); let command = Command::new("continuum-party") + .version(env!("CARGO_PKG_VERSION")) + .long_version(crate::release::described()) .about("A party's client of a federation: signs its events, and votes by its record"); config::with_options(command, config::PARTY_OPTIONS) .subcommand_required(true) |
