From 705e7661abff20fd8fefd8b25320999209378274 Mon Sep 17 00:00:00 2001 From: Chris Sells Date: Tue, 6 Oct 2026 11:22:18 -0700 Subject: [PATCH] docs(upgrading): key the shared-server read failure to schema v53, not release 1.2.0 #7301 scoped the pre-migration read failure on a shared server to schemas that "predate 1.2.0". That misses 1.2.2, the recovery re-release of the 1.1 line: its migrations stop at 0053 with no lease migrations, so a 1.2.2 server sits at v53 like 1.1.x. Upgrading such a server's clients to 1.3.1 without `bd migrate schema` makes `bd list`, `bd show` and `bd ready` fail with `table not found: leases`. Key the caveat to schema v53 or older, naming 1.1.x and 1.2.2, which matches the section's own "A 1.2.2 or 1.1.x database sits at schema v53". Refs #6929, #7284, #7301 --- docs/getting-started/upgrading.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/getting-started/upgrading.md b/docs/getting-started/upgrading.md index daa058bed..da9c5330e 100644 --- a/docs/getting-started/upgrading.md +++ b/docs/getting-started/upgrading.md @@ -445,7 +445,7 @@ Upgrade one server's clients like this: ```bash # 1. Upgrade bd on every client of the server. Reads keep working throughout — # an upgraded client reads the old schema, it just cannot write to it -# (unless the server predates 1.2.0; see below). +# (unless the server's schema is v53 or older; see below). bd version # on each client, confirm the new version # 2. Once, from a workspace already set up against this server: consent. @@ -459,8 +459,8 @@ Between steps 1 and 2, an upgraded client reads normally and its writes are refused with the gate's guidance. Nothing is silently promoted, so there is no deadline — but the window is a degraded one, so keep it short. -If the server's schema predates 1.2.0 (an upgrade from 1.1.x or earlier), -reads can fail too until step 2: `bd list` stops with +If the server's schema is v53 or older (1.1.x, or 1.2.2, the re-release of +the 1.1 line), reads can fail too until step 2: `bd list` stops with `table not found: leases` ([#6929](https://github.com/gastownhall/beads/issues/6929)). Run step 2 as soon as the clients are upgraded.