recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

upstream(matrix-synapse): update notes for 7.3.0+v1.154.0 PR#2

Browse Source
This commit is contained in:
autonomic-bot
2026-06-12 04:00:59 +00:00
parent 4f31abc0c7
commit c7fae6cbee
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
cc-ci-plan/upstream/matrix-synapse.md
View File

@ -13,9 +13,10 @@
## Standing notes
- **pgautoupgrade (main db):** performs in-place `pg_upgrade` on first start of a new major image — no manual dump/restore needed, but always take a DB backup before deploying a major version bump. Current: 17-alpine → 18-alpine in this PR.
- **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.
- **pgautoupgrade (main db):** performs in-place `pg_upgrade` on 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 with `PGDATA=/var/lib/postgresql/data` so 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.
- **MAS 1.18.0:** `device_code_grant_enabled` is now `false` by default — existing deployments using device code grants should set this explicitly in config.
- **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_enabled` is now `false` by 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.