diff --git a/CHANGELOG.md b/CHANGELOG.md index 1cfa105..ff6d00b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -16,12 +16,25 @@ is only released once its **exit criterion** is met, not when its code lands. | v0.9.0 | — | Managing people and the tenancy tree | released | | v0.10.0 | — | InfiniBand fabrics and NVLink, doctor, node add, engines installed by the nodes | released | | v0.11.0 | — | High availability from setup, the setup and console screens, usage sums and per-tenant alerts | released | +| v0.12.0 | — | The cluster's settings in the store, in force when changed; the firewall switch; wipe | released | | v1.0.0 | 5 | Tenancy, prefix affinity, benchmarking | planned | Until v1.0.0 the minor version is the breaking one: configuration formats and Go APIs change between minors without a deprecation period. -## Unreleased +## v0.12.0 — 2026-10-06 + +A minor version, because where the configuration lives changes: everything in +server.yaml that is not one machine's own is now the cluster's settings, kept +in the store, the same on every control plane and in force within seconds of +a change. Nothing needs doing by hand to upgrade. The first control plane to +start on v0.12.0 brings its server.yaml's cluster keys into the store, with +the baseline guard policy when the file had none. From then on, change them +with `llmgw ctl config` or the console's Settings, not in server.yaml, whose +cluster keys are ignored, with a warning. Upgrade every control plane (`llmgw +ctl upgrade` does, the leader last): until the leader runs v0.12.0, +`llmgw ctl config` through a standby is refused. Nodes need v0.12.0 to follow +the firewall switch. ### Changed