From 0abe090ef98d89c8cbab07ea596fac137c7f6bf6 Mon Sep 17 00:00:00 2001 From: autonomic-bot <64+autonomic-bot@noreply.git.autonomic.zone> Date: Fri, 20 Nov 2026 06:14:25 +0000 Subject: [PATCH] upstream(matrix-synapse): add mau.fi blog as mautrix security source --- cc-ci-plan/upstream/matrix-synapse.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/cc-ci-plan/upstream/matrix-synapse.md b/cc-ci-plan/upstream/matrix-synapse.md index e257e80..e88414f 100644 --- a/cc-ci-plan/upstream/matrix-synapse.md +++ b/cc-ci-plan/upstream/matrix-synapse.md @@ -19,4 +19,6 @@ - **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. - **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. +- **mautrix bridges security:** no dedicated security page — monthly release posts at + https://mau.fi/blog/ (e.g. 2026-11 mautrix release) carry any security items alongside features. - **Bridges are optional overlays** (compose.signal.yml, compose.telegram.yml, compose.discord.yml) — only include them in COMPOSE_FILE when actively using bridges.