beads/docs/getting-started
Chris Sells c33d30aa10
docs(upgrading): key the shared-server read failure to schema v53, not release 1.2.0 (#7310)
#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
2026-10-06 11:42:52 -07:00
..
ide-setup.md [codex] Add Kiro setup recipe (#4535) 2026-07-27 22:28:43 -07:00
installation.md docs(troubleshooting): document the two native-Windows integration traps (#5838) 2026-08-20 05:41:39 -07:00
quickstart.md fix(notion): keep notion.token out of the Dolt database (#6676) (#6724) 2026-09-27 14:53:11 -07:00
sync-setup.md docs: pin the Dolt version instead of steering users to releases/latest (ga-m0dlk) (#5899) 2026-08-20 22:41:24 -07:00
upgrading.md docs(upgrading): key the shared-server read failure to schema v53, not release 1.2.0 (#7310) 2026-10-06 11:42:52 -07:00