diff --git a/CHANGELOG.md b/CHANGELOG.md
index 0d8bda6..7e03f8b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,19 @@ one of them changed. An entry says which artefact and which version, so `web 0.1
 Every version published to a channel appears here. Nothing is written from memory afterwards: a build
 cannot be published without its entry.
 
+## 2026-08-31 — Nothing in the console changes, and that is the whole of it `web 0.123.0`
+
+**This is the same console as `web 0.122.0`.** No behaviour changed, no bug was fixed, nothing in
+the interface moved. The two images differ only in the version they report about themselves.
+
+**It exists to exercise a rollout end to end**, against a cluster that is actually serving: a new
+digest pinned, the pods replaced one at a time under a disruption budget, the previous ones still
+answering until the new ones are ready. A rollout path nobody has run is a rollout path nobody
+knows about, and the honest way to learn it is on a build where being wrong costs nothing.
+
+**Nothing to do.** If you are on 0.122.0 there is no reason to take this, and if you take it there
+is nothing to notice. The next entry describes a real change.
+
 ## 2026-08-29 — Keep several conversations on the go, and switch between them `api 0.100.0` `web 0.122.0`
 
 Opening a conversation used to mean being *in* it: to reach another you left it, found the one you