From 724a2959a8a6373458a769688572dadca881b609 Mon Sep 17 00:00:00 2001 From: valgulnecron <39313199+ValgulNecron@users.noreply.github.com> Date: Wed, 11 Nov 2026 21:48:41 +0100 Subject: [PATCH] docs: describe the postgres-availability bucket accurately The roadmap's Postgres paragraph called postgres-availability an upgrade bucket. It tests a combined-install deployment-strategy change and outage recovery with the working-tree chart, not an upgrade from a previous release. Mirrors docs/roadmap.md in GameplanePanel/Gameplane#927. Co-Authored-By: Claude Opus 5.5 Signed-off-by: valgulnecron <39313199+ValgulNecron@users.noreply.github.com> --- src/content/docs/roadmap.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/content/docs/roadmap.mdx b/src/content/docs/roadmap.mdx index 755d26b..02f27b6 100644 --- a/src/content/docs/roadmap.mdx +++ b/src/content/docs/roadmap.mdx @@ -321,8 +321,10 @@ every later migration is one portable file both drivers run builds the api with the tag and runs `api/internal/db`'s tests against a real PostgreSQL server. It stays **experimental** until the rest lands: running the handler/auth/audit test suites against Postgres (the `e2e-postgres` CI job already -runs the auth, roles and RBAC e2e buckets and the `postgres-availability` upgrade -bucket on it), a published image built with `-tags postgres`, and multi-replica +runs the auth, roles and RBAC e2e buckets on it, plus the `postgres-availability` +bucket, a deployment-strategy change and outage recovery on the working-tree +chart, not an upgrade from a previous release), a published image built with +`-tags postgres`, and multi-replica safety (the user-management lock and the audit hash chain assume a single API process).