v26.06

Release post: https://mau.fi/blog/2026-06-mautrix-release/

• Removed support for legacy /v1 provisioning API.
• Updated Telegram API to layer 227.
• Added support for new rich text messages from Telegram.
• Added support for sending arbitrary Lottie stickers to Telegram.
• Added option to bridge videos in Telegram URL previews as normal video messages to Matrix.
• Fixed support for MTProxy proxies.
• Fixed handling too large files from Telegram.
• Fixed usernames getting cleared incorrectly from the bridge database.
• Fixed using imported emoji packs when direct media is enabled.

v26.05

Release post: https://mau.fi/blog/2026-05-mautrix-release/

• Updated Telegram API to layer 225.
• Added support for bridging guest bot messages from Telegram using per-message profiles on Matrix.
• Added support for bridging message reactions from Telegram when logged in as a bot.
• Added support for sending imported animated stickers back to Telegram.
  • Note: packs imported before this change will have to be re-imported.
• Added support for cutting off long messages before sending to Telegram.
• Added support for converting matrix.to event links to t.me links when sending to Telegram.
• Added support for bridging member events from Matrix.
• Fixed mx_room_state table not being migrated correctly from the Python bridge in SQLite databases.
• Fixed username changes of Telegram users not being saved correctly.

v26.04

Release post: https://mau.fi/blog/2026-04-mautrix-release/

• Rewrote bridge in Go using bridgev2 architecture.
  • To migrate the bridge, simply upgrade in-place from v0.15.3 or later. The database and config will be migrated automatically, although some parts of the config aren't migrated (e.g. log config, permission types specific to the legacy bridge). Taking backups beforehand is always recommended.
  • It is recommended to check the config file after upgrading. If you have prevented the bridge from writing to the config, you should update it manually.
  • The old-style relaybot is not yet supported and will not be migrated. Setups using the relaybot will have to manually log in as a bot and use set-relay to enable the generic relay mode. The default_relays config option can be used to allow users to bridge chats through the relay user to emulate the old-style relaybot.
  • For multi-user bridges, normal (mini/non-super) group portal rooms are no longer shared, which means every Matrix user will have their own room. The old room will be assigned to one Matrix user randomly and others will get a new room created automatically when receiving a message in the chat or when using the !tg sync-chats command.
    • If you want shared portals, upgrade the affected groups to supergroups. You can upgrade groups using the !tg upgrade command, or in the official apps by enabling any setting that requires a supergroup (e.g. add a member tag for any admin).
  • Management room status will not be migrated. Use !tg set-management-room after the upgrade to re-allow commands without the !tg prefix in your private chat with the bridge bot.
  • Any migration issues should be reported in the Matrix room linked in the readme.
• Notable new features include:
  • Topic groups are now bridged as spaces
  • Entire sticker and emoji packs can be synced in both directions

Note: the last (unreleased) version of the legacy Python bridge is available in the python-final tag.

v0.15.3

• Updated Telegram API to layer 204.
• Added support for MSC4190.
• Enabled captions by default, as they are now supported by most clients.
  • Existing configs will still need to enable caption_in_message manually.
• Changed new room creation to hardcode room v11 to avoid v12 rooms being created before proper support for them can be added.
• Fixed bridging sticker messages with partial quote replies from Telegram.
• Fixed text in poll bridging.
• Disabled kicking unauthenticated users from portals.

v0.15.2

• Dropped support for Python 3.9.
• Updated Telegram API to layer 183.
• Added support for authenticated media downloads.
• Added support for receiving reactions when using a bot account.
• Added option to limit file size by chat type.
• Fixed reply bridging breaking in some cases.

v0.15.1

• Updated Telegram API to layer 169.
• Updated Docker image to Alpine 3.19.
• Fixed some potential cases where a portal room would be created for the relaybot even if ignore_unbridged_group_chat was enabled.
• Fixed member sync in groups with hidden members causing puppeted Matrix users to be kicked even if they're still in the group.

v0.15.0

• Removed support for MSC2716 backfilling.
• Added add-contact and delete-contact commands.
• Updated Telegram API layer to 166.
  • Includes receiving view-once media, blockquotes, quote replies and other such things
• Fixed AuthKeyNotFound errors not being handled and causing users to get stuck in a non-logged-in state.

v0.14.2

• Security: Updated Pillow to 10.0.1.
• Added support for double puppeting with arbitrary as_tokens. See docs for more info.
• Added support for sending webm and tgs files as stickers.
• Updated to Telegram API layer 161.
• Fixed cached usernames for Telegram users being cleared incorrectly, leading to mentions not being bridged as usernames.
• Fixed reaction bridging failing if the server running the bridge was rebooted less than 12 hours ago.

v0.14.1

Added

• Added option to delete megolm sessions that were received before the automatic ratcheting options were introduced.
• Added config option to use IPv6 for Telegram connection (thanks to @exciler in #920).

Improved

• Dropped support for Python 3.8.
• Updated Docker image to Alpine 3.18.
• Added timeout for forward backfills to prevent it from getting stuck permanently.

Fixed

• Fixed bridge.filter.users config option not being read correctly.
• Fixed proxy support to use python-socks instead of pysocks.

v0.14.0

Added

• Added fallback messages for calls and premium gifts.
• Added options to automatically ratchet/delete megolm sessions to minimize access to old messages.
• Added option to not set room name/avatar even in encrypted rooms.
• Implemented appservice pinging using MSC2659.
• Added option to disable or filter bridging direct chats (thanks to @Steffo99 in #892).
• Added options to specify different limits for forward and catchup backfilling depending on chat type.

Improved

• Improved handling logouts and certain connection errors.
• Changed reaction bridging to preserve timestamps.
• Disabled creating portals for DMs that don't have any messages when sync_direct_chats is enabled.

Fixed

• Fixed syncing mute status when portal is created through incoming message rather than in startup sync.
• Fixed bridge incorrectly trusting member list and kicking users when supergroup has member list hidden.
• Fixed sending messages after creating groups from Matrix using relaybot instead of puppet (thanks to @maltee1 in #902).