diff options
| author | tv <tv@krebsco.de> | 2026-11-18 12:48:29 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-18 13:59:42 +0100 |
| commit | d130c0612b4c63f2d30da65ebcc231018c1f2606 (patch) | |
| tree | 8700f2d53351cbbecbe772ea7701bf6240d5210c /docs/guides/federation/upgrades.md | |
| parent | 0bfe07af92a775b0e896e0fc5a989a1d9b65f7b3 (diff) | |
docs: references to another document's section linked to it
Where a document names a section of another after linking to it
("([`store.md`](store.md), Pinned checkpoints)"), the name links to that
section too, by the id both GitHub and cgit's about filter give its
heading; paragraphs that grew past the width are wrapped anew, links and
code kept on one line each.
Diffstat (limited to 'docs/guides/federation/upgrades.md')
| -rw-r--r-- | docs/guides/federation/upgrades.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md index 95dab12..570de19 100644 --- a/docs/guides/federation/upgrades.md +++ b/docs/guides/federation/upgrades.md @@ -1,17 +1,17 @@ # Upgrades and the federation's number Upgrading the continuum a federated swarm's nodes run, and what the federation's number -in each version says. The rules are the design's -([`federation.md`](../../federation.md), Changing the federation). +in each version says. The rules are the design's ([`federation.md`](../../federation.md), +[Changing the federation](../../federation.md#changing-the-federation)). ## Upgrading continuum A node of a federated swarm upgrades as any node does -([`operations.md`](../../operations.md), Upgrading): one at a time, restarted with its -files. Across a change of the wire format, upgraded nodes and the others don't talk, and -the swarm is split until all are upgraded; a remake needs the same Automerge on every -node, and one with another rejoins instead of switching. Until continuum's first release, -take every upgrade as such a change. +([`operations.md`](../../operations.md), [Upgrading](../../operations.md#upgrading)): one +at a time, restarted with its files. Across a change of the wire format, upgraded nodes +and the others don't talk, and the swarm is split until all are upgraded; a remake needs +the same Automerge on every node, and one with another rejoins instead of switching. Until +continuum's first release, take every upgrade as such a change. Nobody runs every node of a federated swarm: each party's operators upgrade its nodes. Agree on when, among the parties, and upgrade close together. |
