diff options
| author | tv <tv@krebsco.de> | 2026-11-19 15:52:51 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 17:35:13 +0100 |
| commit | 180e5ad1d1d144f5e9f9168094a0ec0417b64a61 (patch) | |
| tree | 9b0d9f2b43f808baa5ab5e0c8bedbb9fcc18abb5 | |
| parent | e83550d088f28a1e69eeeff01b93966ffafba0ca (diff) | |
CHANGELOG.md: notable changes by release, from 0.0.1
From 0.0.1 on, notable changes are logged as they come, under
Unreleased until the next release, each with links to its docs and
code; fixes and internal work that change nothing anyone relies on are
left out. 0.0.1's entry says what the first release to keep it holds.
The README points to it.
| -rw-r--r-- | CHANGELOG.md | 31 | ||||
| -rw-r--r-- | README.md | 2 |
2 files changed, 33 insertions, 0 deletions
diff --git a/CHANGELOG.md b/CHANGELOG.md new file mode 100644 index 0000000..ffc0c13 --- /dev/null +++ b/CHANGELOG.md @@ -0,0 +1,31 @@ +# Changelog + +Notable changes, newest first; fixes and internal work that change nothing anyone relies +on are left out. A release is tagged `v<version>`, and its version says how to upgrade to +it from the release before ([`docs/operations.md`](docs/operations.md), +[Upgrading](docs/operations.md#upgrading)). + +## Unreleased + +## 0.0.1 (2026-11-19) + +The first release to keep this log; a flag day from anything before it. What it holds: + +* A replicated Automerge document, read and written as JSON by path over an HTTP API + ([`docs/api.md`](docs/api.md), [`docs/openapi.yaml`](docs/openapi.yaml)), synced + over Mycelium, libp2p or Tor, one or several at once + ([`docs/transports.md`](docs/transports.md)). +* Remakes, compacting the history by a majority of the members + ([`docs/remakes.md`](docs/remakes.md)). +* Users, tokens, logins by key, and access by path ([`docs/access.md`](docs/access.md)). +* The dashboard ([`docs/dashboard.md`](docs/dashboard.md)). +* Behind the `federation` feature, a swarm kept by parties that don't trust each other, + deciding by two thirds ([`docs/federation.md`](docs/federation.md), the guides in + [`docs/guides/federation/`](docs/guides/federation/README.md), + [`src/federation/`](src/federation/)), and the party's client, `continuum-party`. Its + federation 1 knows revision 1, merge events; `scripts/federation-check` checks a tree + against the release tagged `federation-<F>.<R>` + ([`docs/federation-tests.md`](docs/federation-tests.md)). +* `continuum --version` says the wire versions, the federation's revisions and the + Automerge version a build has, and nodes tell their peers theirs (`knows` in + `GET /peers` and `GET /events/counts`). @@ -79,6 +79,8 @@ curl -u alice:secret localhost:3000/peers # who is out there ## Documentation +What changed from one release to the next: [`CHANGELOG.md`](CHANGELOG.md). + **Running nodes** * [`docs/configuration.md`](docs/configuration.md): options, files and imports (`continuum --help` lists them); |
