aboutsummaryrefslogtreecommitdiffstats
path: root/CHANGELOG.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 18:52:37 +0000
committertv <tv@krebsco.de>2026-11-19 20:12:23 +0100
commitab9d79ba58562bfcd468afe8c2047a1110e34b7c (patch)
tree835ce4e444bcd11ef9d90c8f70f2c297e128cecb /CHANGELOG.md
parent97b9c45e5f8b7eed61dd494b977d27790a9544e2 (diff)
continuum-party: propose admit, remove, give, take, keys, nodes, checkpoint, revision
The changes made most no longer go through `next`, jq and a file: each is a subcommand of `propose`, which writes the next version changed so (Intent, intended) and proposes it. * admit PARTY --keys KEY|FILE... [--nodes NODE...]: its keys and node list named anew since the new number; a party already, or no party's name, refused. * remove PARTY: its keys, node list and the rules giving it places go. * give PATH PARTY|{party}: a rule first; one of that path before goes. * take PATH: the rule of that path goes, and where another rule may still give one of its places (overlaps), a rule giving them to nobody goes first. * keys PARTY KEY|FILE..., nodes PARTY NODE...: named anew. * checkpoint: at the heads the node shows. * revision FEATURE: as `next --revision`. Keys are authorized_keys lines, or files of them. Every proposal, a file's too, now says what its version does first (version_lines, shared with `show`) and asks on a terminal; with --yes the one question covers the vote, which then says and asks nothing more. A version changing only its number isn't proposed. --print writes the version instead, to change by hand and propose as a file.
Diffstat (limited to 'CHANGELOG.md')
-rw-r--r--CHANGELOG.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 76bc09a..b2664b6 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,13 @@ it from the release before ([`docs/operations.md`](docs/operations.md),
## Unreleased
+* `continuum-party propose` takes the changes made most by what they are for: `admit`,
+ `remove`, `give`, `take`, `keys`, `nodes`, `checkpoint` and `revision` write the next
+ version so and propose it. Every proposal says first what it does, and asks on a
+ terminal; `--print` writes the version instead
+ ([`docs/guides/federation/common-changes.md`](docs/guides/federation/common-changes.md);
+ [`src/federation/party.rs`](src/federation/party.rs)).
+
* `scripts/wire-check` runs a swarm of the last release's nodes and this tree's on one
host, and checks they talk where their wire versions meet, and say so where they
don't; `scripts/release` runs it ([`docs/development.md`](docs/development.md),