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 /docs | |
| 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 'docs')
| -rw-r--r-- | docs/operations.md | 13 |
1 files changed, 13 insertions, 0 deletions
diff --git a/docs/operations.md b/docs/operations.md index 0502782..97fee26 100644 --- a/docs/operations.md +++ b/docs/operations.md @@ -109,6 +109,19 @@ how to upgrade to it from the release before: Before 1.0.0, any release may be a flag day; its tag's message says whether it is. +What decides which builds work together, a build says (`-V` the release alone): the wire +versions it speaks, the federation and the revisions of it it knows (with the +`federation` feature), and the Automerge it makes documents with. `continuum-party +--version` says the same. + +```sh +continuum --version +# continuum 1.0.0 +# wire versions 52 to 52 +# federation 1: the base revision, revision 1 (merge-events) +# automerge 0.12.0 +``` + A node upgrades by restarting with its files. What to know: * **The wire format.** Each change to it bumps a version byte, and nodes ignore |
