Per default relay bot functionality is disabled; the bridge user permissions depends on the relay bot, if enabled the base domain users are on level relay, else remain on user;

Enable / disable relay bot functionality as configuratoin paramter; set bridge permissions for base domain users to user level

Update matrix-mautrix-signal config to 0.2.0 to enable relay mode

Allow configuring synapse database transaction limit

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1225

Update Synapse (1.39.0 -> 1.40.0)

irc appservice image tag has a 'v' now

New version of Mautrix Signal bridge (version 0.2.0)

Update IRC appservice

https://github.com/matrix-org/matrix-appservice-irc/releases/tag/0.29.0

whatsapp bridge has new docker image location

See https://github.com/mautrix/whatsapp/releases/tag/v0.1.8

Upgrade Hydrogen (0.2.3 -> 0.2.5)

Regression since 421f85defa

Update howto-server-delegation.md

The default of using the `matrix` database is better anyway.

The attached code for the "Serving the Federation API with your certificates and matrix-nginx-proxy" section suggests using the matrix.<your-domain> certificate for the federation API as opposed to the necessary <your-domain> certificate for the federation to work. This can cause some confusion to readers.

Updating to ma1sd v2.5.0

Related to https://github.com/spantaleev/matrix-docker-ansible-deploy/pull/1171

GoMatrixHosting v0.5.5

Update configuring-well-known.md

Added selfbuild functionality to matrix-reminder-bot

All of `setup_install.yml` only runs if `matrix_bot_matrix_reminder_bot_enabled`,
so it's not necessary to add that condition once again.

Restore authentication for Jitsi Meet

Update prometheus node exporter (1.1.2 -> 1.2.0)

Fixed self-build functionality for mautrix-signal

We'd rather not suppress pull errors or run self-build tasks if pulling fails.

Jitsi Update -> stable-5963