Skip to content

docs: describe the postgres-availability bucket accurately #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ValgulNecron merged 1 commit into from
Nov 12, 2026
Merged

docs: describe the postgres-availability bucket accurately #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions src/content/docs/roadmap.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).

Expand Down