Releases: mautrix/python
Releases · mautrix/python
v0.18.6
v0.18.5
v0.18.4
- (client.api) Added option to pass custom data to
/createRoomto enable using custom fields and testing MSCs without changing the library. - (client.api) Updated MSC3870 support to send file name in upload complete call.
- (types) Changed
set_editto clear reply metadata as edits can't change the reply status. - (util.formatter) Fixed edge case causing negative entity lengths when splitting entity strings.
v0.18.3
- (util.async_db) Fixed mistake in default no-op database error handler causing the wrong exception to be raised.
- (crypto.store.asyncpg) Updated
put_group_sessionto catch unique key errors and log instead of raising. - (client.api) Updated MSC3870 support to catch and retry on all connection errors instead of only non-200 status codes when uploading.
v0.18.2
v0.18.1
v0.18.0
- Breaking change (util.async_db) Added checks to prevent calling
.start()on a database multiple times. - (appservice) Fixed MSC2409 support to read to-device events from the correct field.
- (appservice) Added support for automatically calling functions when a transaction contains MSC2409 to-device events or MSC3202 encryption data.
- (bridge) Added option to use MSC2409 and MSC3202 for end-to-bridge encryption. However, this may not work with the Synapse implementation as it hasn't been tested yet.
- (bridge) Replaced
homeserver->asmuxflag with more genericsoftwarefield. - (bridge) Added support for overriding parts of config with environment variables.
- If the value starts with
json::, it'll be parsed as JSON instead of using as a raw string.
- If the value starts with
- (client.api) Added support for MSC3870 for both uploading and downloading media.
- (types) Added
knock_restrictedjoin rule toJoinRuleenum. - (crypto) Added warning logs if claiming one-time keys for other users fails.
v0.17.8
v0.17.7
- (util.async_db) Added
init_commandsto run commands on each SQLite connection (e.g. to enablePRAGMAs). No-op on Postgres. - (bridge) Added check to make sure e2ee keys are intact on server. If they aren't, the crypto database will be wiped and the bridge will stop.