Deferred to separate PR: mautrix/signal + mautrix/telegram CalVer upgrades (+ signaldb/telegramdb PG bumps)
⚠️ Operator Actions Required
1. Backup main DB before deploying — pgautoupgrade 17→18 performs an in-place cluster upgrade. Take a backup first: abra app run YOURDOMAIN db pg_dump -U synapse synapse > synapse.sql
The PGDATA env pin (PGDATA=/var/lib/postgresql/data) ensures pgautoupgrade finds the existing cluster.
2. Discorddb users only — postgres:13→16 is a plain postgres service (not pgautoupgrade), so it requires manual dump/restore before upgrading. If you use the discord bridge: pg_dump -U discordbridge discordbridge > discordbridge.sql
Then restore after the upgrade.
3. MAS 1.18.0 device code grants — oauth.device_code_grant_enabled now defaults to false. If your deployment uses device code grants, add device_code_grant_enabled: true under the oauth: section in mas.config.yaml.tmpl before upgrading.
Release notes summary
Synapse v1.150–v1.154: postgres statement timeout reduced 1h→10min; no breaking config changes for standard single-process installs
MAS 1.15–1.18: device_code_grant_enabled default change only; no DB migrations
nginx 1.31.1: maintenance release
pgautoupgrade 18-alpine: PGDATA path change in postgres:18 — patched with PGDATA env pin (verified working on cc-ci)
## matrix-synapse upgrade: 7.1.1+v1.149.1 → 7.3.0+v1.154.0
### Image changes
| service | current | new |
|---------|---------|-----|
| app (synapse) | matrixdotorg/synapse:v1.149.1 | matrixdotorg/synapse:v1.154.0 |
| db | pgautoupgrade/pgautoupgrade:17-alpine | pgautoupgrade/pgautoupgrade:18-alpine |
| web | nginx:1.29.6 | nginx:1.31.1 |
| mas | ghcr.io/element-hq/matrix-authentication-service:1.14.0 | 1.18.0 |
| discorddb | postgres:13-alpine | postgres:16-alpine |
Deferred to separate PR: mautrix/signal + mautrix/telegram CalVer upgrades (+ signaldb/telegramdb PG bumps)
### ⚠️ Operator Actions Required
**1. Backup main DB before deploying** — pgautoupgrade 17→18 performs an in-place cluster upgrade. Take a backup first:
`abra app run YOURDOMAIN db pg_dump -U synapse synapse > synapse.sql`
The PGDATA env pin (`PGDATA=/var/lib/postgresql/data`) ensures pgautoupgrade finds the existing cluster.
**2. Discorddb users only** — postgres:13→16 is a plain postgres service (not pgautoupgrade), so it requires manual dump/restore before upgrading. If you use the discord bridge:
`pg_dump -U discordbridge discordbridge > discordbridge.sql`
Then restore after the upgrade.
**3. MAS 1.18.0 device code grants** — `oauth.device_code_grant_enabled` now defaults to `false`. If your deployment uses device code grants, add `device_code_grant_enabled: true` under the `oauth:` section in `mas.config.yaml.tmpl` before upgrading.
### Release notes summary
- **Synapse v1.150–v1.154**: postgres statement timeout reduced 1h→10min; no breaking config changes for standard single-process installs
- **MAS 1.15–1.18**: device_code_grant_enabled default change only; no DB migrations
- **nginx 1.31.1**: maintenance release
- **pgautoupgrade 18-alpine**: PGDATA path change in postgres:18 — patched with PGDATA env pin (verified working on cc-ci)
### Verified on cc-ci (chaos deploy)
All 3 services converged healthy: synapse v1.154.0 ✓, pgautoupgrade:18-alpine (pg17→18 upgrade completed) ✓, nginx:1.31.1 ✓
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
matrix-synapse upgrade: 7.1.1+v1.149.1 → 7.3.0+v1.154.0
Image changes
Deferred to separate PR: mautrix/signal + mautrix/telegram CalVer upgrades (+ signaldb/telegramdb PG bumps)
⚠️ Operator Actions Required
1. Backup main DB before deploying — pgautoupgrade 17→18 performs an in-place cluster upgrade. Take a backup first:
abra app run YOURDOMAIN db pg_dump -U synapse synapse > synapse.sqlThe PGDATA env pin (
PGDATA=/var/lib/postgresql/data) ensures pgautoupgrade finds the existing cluster.2. Discorddb users only — postgres:13→16 is a plain postgres service (not pgautoupgrade), so it requires manual dump/restore before upgrading. If you use the discord bridge:
pg_dump -U discordbridge discordbridge > discordbridge.sqlThen restore after the upgrade.
3. MAS 1.18.0 device code grants —
oauth.device_code_grant_enablednow defaults tofalse. If your deployment uses device code grants, adddevice_code_grant_enabled: trueunder theoauth:section inmas.config.yaml.tmplbefore upgrading.Release notes summary
Verified on cc-ci (chaos deploy)
All 3 services converged healthy: synapse v1.154.0 ✓, pgautoupgrade:18-alpine (pg17→18 upgrade completed) ✓, nginx:1.31.1 ✓
Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.
cc @trav @notplants
!testme
🌻 cc-ci —
matrix-synapse@72f0176a✅ passedfull logs · dashboard
Superseded by #3 (version corrected to 7.2.0, discord postgres bump dropped). Closing.
Pull request closed