recipe-maintainers/matrix-synapse
0
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

chore: upgrade bridges + bridge DBs #5

Open
autonomic-bot wants to merge 1 commits from upgrade-c04a858 into main
pull from: upgrade-c04a858
merge into: recipe-maintainers:main
Conversation 4 Commits 1 Files Changed 5 +593 -512
autonomic-bot commented 2026-06-23 01:55:39 +00:00
Owner
Copy Link

Bridge + bridge DB upgrade

service image current new
signalbridge dock.mau.dev/mautrix/signal v0.8.7 v0.2606.0
telegrambridge dock.mau.dev/mautrix/telegram v0.15.3 v0.2606.0
signaldb postgres 13-alpine 14-alpine
telegramdb postgres 13-alpine 14-alpine
discorddb postgres 13-alpine 14-alpine

Upstream release notes

What changed and why

signalbridge v0.8.7 → v0.2606.0 — calver scheme change only. mautrix/signal moved from semver (v0.x) to calver (vYY.MM.x) at v25.10 (Oct 2025). The bridge was already Go-based in v0.8.7; the calver switch is a versioning-scheme change, NOT a rewrite. Config schema unchanged; two new optional sections (analytics, env_config_prefix) default to disabled. No template change needed.

telegrambridge v0.15.3 → v0.2606.0 — Python→Go (bridgev2) rewrite at v26.04 (April 2026). v0.15.3 is the last Python release. telegram_bridge.yaml.tmpl rewritten to Go bridgev2 format. Breaking changes for operators:

  • Permission levels renamed: relaybot→relay, user→commands, puppeting→user, full→user
  • Old-style relaybot not supported; use set-relay + default_relays for relay mode
  • telegram.bot_token and homeserver.verify_ssl removed from config
  • Normal (non-super) group portal rooms no longer shared; upgrade affected groups to supergroups
  • Management room status not migrated; re-set with !tg set-management-room
  • .env.sample TELEGRAM_BRIDGE_PERMISSIONS default updated relaybot→relay

signaldb / telegramdb / discorddb postgres 13-alpine → 14-alpine — PG13 EOL Nov 2025. Conservative one-major bump (PG14 supported until Nov 2026). These bridge DBs use plain postgres (not pgautoupgrade), so a major-version bump requires manual dump/restore for operators with existing data.

Operator action required

  • Telegram bridge: review config after upgrade. If using relaybot, switch to relay mode (set-relay). If using non-super groups, upgrade to supergroups (!tg upgrade).
  • Bridge DBs: dump each bridge DB before deploying (plain postgres does NOT auto-upgrade across majors): 
    pg_dump -U signalbridge signalbridge > signal_backup.sql
pg_dump -U telegrambridge telegrambridge > telegram_backup.sql
pg_dump -U discordbridge discordbridge > discord_backup.sql

Recommended release command

abra recipe release matrix-synapse -y

(-y minor: core synapse app unchanged, but telegram bridge Python→Go rewrite is a breaking change for overlay users. Operator may choose -x major.)

Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review.

cc @trav @notplants

## Bridge + bridge DB upgrade | service | image | current | new | |---------|-------|---------|-----| | signalbridge | dock.mau.dev/mautrix/signal | v0.8.7 | v0.2606.0 | | telegrambridge | dock.mau.dev/mautrix/telegram | v0.15.3 | v0.2606.0 | | signaldb | postgres | 13-alpine | 14-alpine | | telegramdb | postgres | 13-alpine | 14-alpine | | discorddb | postgres | 13-alpine | 14-alpine | ### Upstream release notes - **signalbridge** v0.8.7→v0.2606.0: https://github.com/mautrix/signal/releases - **telegrambridge** v0.15.3→v0.2606.0: https://github.com/mautrix/telegram/releases (esp. v26.04 Python→Go rewrite) - **postgres** 13→14: https://www.postgresql.org/docs/release/ ### What changed and why **signalbridge v0.8.7 → v0.2606.0** — calver scheme change only. mautrix/signal moved from semver (v0.x) to calver (vYY.MM.x) at v25.10 (Oct 2025). The bridge was already Go-based in v0.8.7; the calver switch is a versioning-scheme change, NOT a rewrite. Config schema unchanged; two new optional sections (analytics, env_config_prefix) default to disabled. No template change needed. **telegrambridge v0.15.3 → v0.2606.0** — Python→Go (bridgev2) rewrite at v26.04 (April 2026). v0.15.3 is the last Python release. `telegram_bridge.yaml.tmpl` rewritten to Go bridgev2 format. Breaking changes for operators: - Permission levels renamed: `relaybot`→`relay`, `user`→`commands`, `puppeting`→`user`, `full`→`user` - Old-style relaybot not supported; use `set-relay` + `default_relays` for relay mode - `telegram.bot_token` and `homeserver.verify_ssl` removed from config - Normal (non-super) group portal rooms no longer shared; upgrade affected groups to supergroups - Management room status not migrated; re-set with `!tg set-management-room` - `.env.sample` `TELEGRAM_BRIDGE_PERMISSIONS` default updated `relaybot`→`relay` **signaldb / telegramdb / discorddb postgres 13-alpine → 14-alpine** — PG13 EOL Nov 2025. Conservative one-major bump (PG14 supported until Nov 2026). These bridge DBs use **plain postgres** (not pgautoupgrade), so a major-version bump requires manual dump/restore for operators with existing data. ### Operator action required - **Telegram bridge**: review config after upgrade. If using relaybot, switch to relay mode (`set-relay`). If using non-super groups, upgrade to supergroups (`!tg upgrade`). - **Bridge DBs**: dump each bridge DB before deploying (plain postgres does NOT auto-upgrade across majors): ``` pg_dump -U signalbridge signalbridge > signal_backup.sql pg_dump -U telegrambridge telegrambridge > telegram_backup.sql pg_dump -U discordbridge discordbridge > discord_backup.sql ``` ### Recommended release command ``` abra recipe release matrix-synapse -y ``` (-y minor: core synapse app unchanged, but telegram bridge Python→Go rewrite is a breaking change for overlay users. Operator may choose -x major.) Tested green on the cc-ci recipe CI server (full suite, cold, against this PR head). NOT merged — for operator review. cc @trav @notplants
autonomic-bot added 1 commit 2026-06-23 01:55:39 +00:00
chore: upgrade bridges + bridge DBs
All checks were successful
cc-ci/testme cc-ci: success
Details
c04a8583bf 
signalbridge: v0.8.7 -> v0.2606.0 (calver scheme change, already Go-based)
telegrambridge: v0.15.3 -> v0.2606.0 (Python->Go bridgev2 rewrite; config template rewritten)
signaldb/telegramdb/discorddb: postgres 13-alpine -> 14-alpine (PG13 EOL; conservative one-major bump)
.env.sample: TELEGRAM_BRIDGE_PERMISSIONS relaybot -> relay (Go bridgev2 permission rename)
autonomic-bot requested review from trav 2026-06-23 01:55:39 +00:00
autonomic-bot requested review from notplants 2026-06-23 01:55:39 +00:00
autonomic-bot commented 2026-06-23 01:55:47 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-23 01:55:48 +00:00
Author
Owner
Copy Link

🌻 cc-ci — matrix-synapse @ c04a8583 ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `matrix-synapse` @ `c04a8583` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/955/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/955) [![level](https://ci.commoninternet.net/runs/955/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/955) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/955) · [dashboard](https://ci.commoninternet.net/)
autonomic-bot commented 2026-06-29 01:54:12 +00:00
Author
Owner
Copy Link

!testme

!testme
autonomic-bot commented 2026-06-29 01:54:34 +00:00
Author
Owner
Copy Link

🌻 cc-ci — matrix-synapse @ c04a8583 ✅ passed

cc-ci result card

level

full logs · dashboard

<!-- cc-ci:testme --> 🌻 **cc-ci** — `matrix-synapse` @ `c04a8583` ✅ **passed** [![cc-ci result card](https://ci.commoninternet.net/runs/966/summary.png)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/966) [![level](https://ci.commoninternet.net/runs/966/badge.svg)](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/966) [full logs](https://drone.ci.commoninternet.net/recipe-maintainers/cc-ci/966) · [dashboard](https://ci.commoninternet.net/)
All checks were successful
cc-ci/testme cc-ci: success
Details
This pull request can be merged automatically.
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin upgrade-c04a858:upgrade-c04a858
git checkout upgrade-c04a858
Sign in to join this conversation.
Reviewers
No Reviewers
trav
notplants
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
autonomic autonomic-bot notplants trav
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: recipe-maintainers/matrix-synapse#5
No description provided.
Delete Branch "upgrade-c04a858"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?