diff options
| author | tv <tv@krebsco.de> | 2026-11-18 11:50:43 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 12:59:11 +0100 |
| commit | 1c0ad4202d971a3555157c2babc07999d166959d (patch) | |
| tree | f413efe7f137c0d52d07a1e657688ca60a80b405 /docs/guides/federation/common-changes.md | |
| parent | aa77c10a8a20356c277e511e9c6e33c98c9b4104 (diff) | |
continuum-party next: the version after the current one, to change
`next` prints the current version numbered on, naming its hash as the
version it changes, and without the checkpoint it names, whose heads are
behind: what a party changes and proposes. The guides begin a version
with it.
Diffstat (limited to 'docs/guides/federation/common-changes.md')
| -rw-r--r-- | docs/guides/federation/common-changes.md | 4 |
1 files changed, 1 insertions, 3 deletions
diff --git a/docs/guides/federation/common-changes.md b/docs/guides/federation/common-changes.md index 2e5861e..acbd98a 100644 --- a/docs/guides/federation/common-changes.md +++ b/docs/guides/federation/common-changes.md @@ -12,9 +12,7 @@ hash as `changes`, and no `checkpoint` (a version names one only to move the sto on, and the current version's heads are behind): ```sh -curl -s -u tv:secret localhost:3000/events/counts | - jq '.version as $v | $v.version | .number += 1 | .changes = $v.hash | del(.checkpoint)' \ - > next.json +continuum-party --node http://tv:secret@localhost:3000 next > next.json ``` Each recipe is a `jq` filter on that file; then propose the result, and vote. |
