Merge pull request #56 from YunoHost-Apps/ci-auto-update-v0.15.0

Upgrade to version 0.15.0

README.md

@@ -19,7 +19,7 @@ If you don't have YunoHost, please consult [the guide](https://yunohost.org/#/in
 A puppeting bridge between Matrix and Telegram packaged as a YunoHost service. Messages, notifications (and sometimes media) are bridged between a Telegram user and a Matrix user. Currently the Matrix user can NOT invite other Matrix user in a bridged Telegram room, so only someone with a Telegram account can participate to Telegram group conversations. The ["Mautrix-Telegram"](https://docs.mau.fi/bridges/python/telegram/index.html) bridge is a Synapse App Service and relies on postgresql. Therefore, [Synapse for YunoHost](https://github.com/YunoHost-Apps/synapse_ynh) should be installed beforehand.
 
 
-**Shipped version:** 0.14.2~ynh1
+**Shipped version:** 0.15.0~ynh1
 ## Documentation and resources
 
 * Official app website: <https://docs.mau.fi/bridges/python/telegram/index.html>

README_fr.md

@@ -22,7 +22,7 @@ La passerelle ["Mautrix-Telegram"](https://docs.mau.fi/bridges/python/telegram/i
 ** Attention : sauvegardez et restaurez toujours les deux applications Yunohost matrix-synapse et mautrix_telegram en même temps!**
 
 
-**Version incluse :** 0.14.2~ynh1
+**Version incluse :** 0.15.0~ynh1
 ## Documentations et ressources
 
 * Site officiel de l’app : <https://docs.mau.fi/bridges/python/telegram/index.html>

conf/config.yaml

@@ -325,6 +325,8 @@ bridge:
   # Disable generating reply fallbacks? Some extremely bad clients still rely on them,
   # but they're being phased out and will be completely removed in the future.
   disable_reply_fallbacks: false
+  # Should cross-chat replies from Telegram be bridged? Most servers and clients don't support this.
+  cross_room_replies: false
   # Whether or not the bridge should send a read receipt from the bridge bot when a message has
   # been sent to Telegram.
   delivery_receipts: false
@@ -360,23 +362,6 @@ bridge:
   backfill:
     # Allow backfilling at all?
     enable: true
-    # Use MSC2716 for backfilling?
-    #
-    # This requires a server with MSC2716 support, which is currently an experimental feature in Synapse.
-    # It can be enabled by setting experimental_features -> msc2716_enabled to true in homeserver.yaml.
-    msc2716: false
-    # Use double puppets for backfilling?
-    #
-    # If using MSC2716, the double puppets must be in the appservice's user ID namespace
-    # (because the bridge can't use the double puppet access token with batch sending).
-    #
-    # Even without MSC2716, bridging old messages with correct timestamps requires the double
-    # puppets to be in an appservice namespace, or the server to be modified to allow
-    # overriding timestamps anyway.
-    #
-    # Also note that adding users to the appservice namespace may have unexpected side effects,
-    # as described in https://docs.mau.fi/bridges/general/double-puppeting.html#appservice-method
-    double_puppet_backfill: false
     # Whether or not to enable backfilling in normal groups.
     # Normal groups have numerous technical problems in Telegram, and backfilling normal groups
     # will likely cause problems if there are multiple Matrix users in the group.
@@ -384,10 +369,9 @@ bridge:
     # If a backfilled chat is older than this number of hours, mark it as read even if it's unread on Telegram.
     # Set to -1 to let any chat be unread.
     unread_hours_threshold: 720
-    # Forward backfilling limits. These apply to both MSC2716 and legacy backfill.
+    # Forward backfilling limits.
     #
     # Using a negative initial limit is not recommended, as it would try to backfill everything in a single batch.
-    # MSC2716 and the incremental settings are meant for backfilling everything incrementally rather than at once.
     forward_limits:
       # Number of messages to backfill immediately after creating a portal.
       initial:
@@ -403,7 +387,7 @@ bridge:
         channel: 100
     # Timeout for forward backfills in seconds. If you have a high limit, you'll have to increase this too.
     forward_timeout: 900
-    # Settings for incremental backfill of history. These only apply when using MSC2716.
+    # Settings for incremental backfill of history. These only apply to Beeper, as upstream abandoned MSC2716.
     incremental:
       # Maximum number of messages to backfill per batch.
       messages_per_batch: 100

doc/PRE_UPGRADE.d/v0.15.0.md

@@ -0,0 +1,2 @@
+This version removes support for MSC2716 backfilling so the values `backfill: msc2716` and `backfill: double_puppet_backfill` in `config.yaml` are removed.
+If you are using those, adjust your configuration before upgrading.

doc/PRE_UPGRADE.d/v0.15.0_es.md

@@ -0,0 +1,2 @@
+Esta versión elimina el soporte para MSC2716 backfilling, por lo que se eliminan los valores `backfill: msc2716` y `backfill: double_puppet_backfill` en `config.yaml`.
+Si los utiliza, ajuste la configuración antes de actualizar.

doc/PRE_UPGRADE.d/v0.15.0_fr.md

@@ -0,0 +1,2 @@
+Cette version supprime le support du backfilling MSC2716, donc les valeurs `backfill : msc2716` et `backfill : double_puppet_backfill` dans `config.yaml` sont supprimées.
+Si vous utilisez ces valeurs, ajustez votre configuration avant la mise à jour.

manifest.toml

@@ -3,7 +3,7 @@ id = "mautrix_telegram"
 name = "Matrix-Telegram bridge"
 description.en = "Telegram puppeting bridge for Matrix/Synapse"
 description.fr = "Passerelle Telegram pour Matrix/Synapse"
-version = "0.14.2~ynh1"
+version = "0.15.0~ynh1"
 maintainers = ["thardev"]
 
 [upstream]
@@ -125,9 +125,9 @@ main.default = 29317
 in_subdir = true
 extract = false
 rename = "mautrix-telegram.tar.gz"
-amd64.url = "https://github.com/mautrix/telegram/archive/refs/tags/v0.14.2.tar.gz"
+amd64.url = "https://github.com/mautrix/telegram/archive/refs/tags/v0.15.0.tar.gz"
-amd64.sha256 = "8071beb09970d7a337e1a1f7700ecd3f4ef774ba51f2e7199f0216883f023786"
+amd64.sha256 = "93060a58be005f441402e569d9ba3ad84bdc51e551a2e2d40b5e7e2b01f2413e"
-arm64.url = "https://github.com/mautrix/telegram/archive/refs/tags/v0.14.2.tar.gz"
+arm64.url = "https://github.com/mautrix/telegram/archive/refs/tags/v0.15.0.tar.gz"
-arm64.sha256 = "8071beb09970d7a337e1a1f7700ecd3f4ef774ba51f2e7199f0216883f023786"
+arm64.sha256 = "93060a58be005f441402e569d9ba3ad84bdc51e551a2e2d40b5e7e2b01f2413e"
-armhf.url = "https://github.com/mautrix/telegram/archive/refs/tags/v0.14.2.tar.gz"
+armhf.url = "https://github.com/mautrix/telegram/archive/refs/tags/v0.15.0.tar.gz"
-armhf.sha256 = "8071beb09970d7a337e1a1f7700ecd3f4ef774ba51f2e7199f0216883f023786"
+armhf.sha256 = "93060a58be005f441402e569d9ba3ad84bdc51e551a2e2d40b5e7e2b01f2413e"