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

upstream(matrix-synapse): document signalbridge calver tag-form gotcha (abra blind spot)

Browse Source
This commit is contained in:
autonomic-bot
2026-07-13 23:20:33 +00:00
parent 4f2dd96c85
commit 89af8e4ed3
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@ -14,7 +14,7 @@
## Standing notes ## 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. **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. - **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 (v25.xx.x / v26.xx.x) at v25.10 (Oct 2025). The bridge was **already Go-based** in v0.8.7 — the calver switch is a versioning-scheme change only, NOT a rewrite. Config schema is unchanged; two new optional sections (`analytics`, `env_config_prefix`) default to disabled. Target: v0.8.7 → v0.2606.0. - **signalbridge calver scheme change:** mautrix/signal moved from semver (v0.x) to calver (v25.xx.x / v26.xx.x) at v25.10 (Oct 2025). The bridge was **already Go-based** in v0.8.7 — the calver switch is a versioning-scheme change only, NOT a rewrite. Config schema is unchanged; two new optional sections (`analytics`, `env_config_prefix`) default to disabled. **Tag-form gotcha (abra blind spot):** the git/docker tags are `v0.YYMM.P` (e.g. `v0.2606.0` = v26.06 = June 2026, LATEST), but the recipe historically also uses the display-name tag `v26.02.2` (= `v0.2602.2`, Feb 2026). abra parses `v26.02.2` as (26,02,2) > `v0.2606.0` as (0,2606,0) and reports "no upgrade" — **always cross-check the GitHub releases page** (https://github.com/mautrix/signal/releases) for this image; the newest tag is the max `YYMM` in the `v0.YYMM.P` form. Both tag forms resolve on dock.mau.dev. Target: v0.8.7 → v0.2606.0.
- **telegrambridge Python→Go rewrite:** mautrix/telegram was **rewritten from Python to Go (bridgev2)** in v26.04 (April 2026). v0.15.3 is the last Python release. The Go bridge auto-migrates DB+config in-place from v0.15.3+, BUT only if config is writable — in this recipe the config is a read-only Docker config, so the **config template must be rewritten** to Go bridgev2 format. Permission levels renamed: `relaybot`→`relay`, `user`→`commands`, `puppeting`→`user`, `full`→`user`. Old-style relaybot not supported. `telegram.bot_token` removed from config. `homeserver.verify_ssl` removed. Target: v0.15.3 → v0.2606.0. - **telegrambridge Python→Go rewrite:** mautrix/telegram was **rewritten from Python to Go (bridgev2)** in v26.04 (April 2026). v0.15.3 is the last Python release. The Go bridge auto-migrates DB+config in-place from v0.15.3+, BUT only if config is writable — in this recipe the config is a read-only Docker config, so the **config template must be rewritten** to Go bridgev2 format. Permission levels renamed: `relaybot`→`relay`, `user`→`commands`, `puppeting`→`user`, `full`→`user`. Old-style relaybot not supported. `telegram.bot_token` removed from config. `homeserver.verify_ssl` removed. Target: v0.15.3 → v0.2606.0.
- **signaldb / telegramdb / discorddb (postgres:13-alpine → 14-alpine):** plain postgres (not pgautoupgrade), so major upgrades require manual dump/restore. PG13 EOL Nov 2025. Conservative one-major bump 13→14 (PG14 EOL Nov 2026); operators with existing data must dump/restore before deploying. - **signaldb / telegramdb / discorddb (postgres:13-alpine → 14-alpine):** plain postgres (not pgautoupgrade), so major upgrades require manual dump/restore. PG13 EOL Nov 2025. Conservative one-major bump 13→14 (PG14 EOL Nov 2026); operators with existing data must dump/restore before deploying.
- **discorddb postgres 13→16:** shipped in PR#2. Plain postgres — operators must dump/restore discorddb before deploying if using the discord bridge. - **discorddb postgres 13→16:** shipped in PR#2. Plain postgres — operators must dump/restore discorddb before deploying if using the discord bridge.