From 114a006df17c52f631daa8ae4a1f043deb0f4317 Mon Sep 17 00:00:00 2001 From: Luxit Date: Fri, 21 Aug 2026 15:06:13 +0200 Subject: [PATCH] Sync the self-hosting stack --- CHANGELOG.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index ecb6ce9..1e68c40 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -9,6 +9,22 @@ 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. +## api 0.82.0 · web 0.103.0 · agent 0.27.0 — 2026-08-21 + +**Nothing changes in what these builds do.** They are identical in behaviour to api 0.81.0, +web 0.102.0 and agent 0.26.0, rebuilt so that every published image carries the same set of +registry labels: what the image is, where its documentation lives, and a link to this file. The +package page in the registry now says something useful to somebody who lands on it without +context. + +Upgrading is worthwhile only for that. If you are running the previous three and reading this, +you already have everything they do. + +**The earlier version tags have been removed from the registry.** Every build before these three +is gone; the `stable`, `dev` and `latest` channels point at them. If you had pinned an exact +older version in `.env`, that pin no longer resolves and `docker compose pull` will fail — pin +one of the versions above instead, or drop the pin to follow `stable`. + ## api 0.81.0 — 2026-08-21 **Approving a plan now actually authorises it.** When Jarvis asks for consent on a whole plan and you