2.7 KiB
2.7 KiB
Upstream sources — matrix-synapse
Standing notes
- pgautoupgrade (main db): performs in-place
pg_upgradeon first start of a new major image — no manual dump/restore needed, but always take a DB backup before deploying a major version bump. PG17→18 shipped in PR#2 (7.3.0+v1.154.0). PGDATA pin required: postgres:18 moved default PGDATA to/var/lib/postgresql/18/docker; pin withPGDATA=/var/lib/postgresql/dataso pgautoupgrade upgrades in place. - signalbridge calver scheme change: mautrix/signal moved from semver (v0.x) to calver (v26.xx.x) after v0.8.7. The v26.x series requires a fresh install or manual Postgres 13→17+ dump/restore for the signaldb sidecar. Deferred to a separate PR.
- telegrambridge calver scheme change: mautrix/telegram moved from v0.15.x to v0.2605.x (calver). Deferred to a separate PR.
- signaldb / telegramdb (postgres:13-alpine → 17-alpine): plain postgres (not pgautoupgrade), so major upgrades require manual dump/restore. Deferred along with the bridge upgrades.
- discorddb postgres 13→16: shipped in PR#2. Plain postgres — operators must dump/restore discorddb before deploying if using the discord bridge.
- MAS 1.18.0:
device_code_grant_enabledis nowfalseby default — existing deployments using device code grants should set this explicitly in config. Shipped in PR#2. - Bridges are optional overlays (compose.signal.yml, compose.telegram.yml, compose.discord.yml) — only include them in COMPOSE_FILE when actively using bridges.