From b7e67e01a447f0cfbbaf219ddf2585ed443d36b9 Mon Sep 17 00:00:00 2001 From: anoadragon453 Date: Thu, 27 Oct 2022 18:30:04 +0000 Subject: deploy: aa70556699e649f46f51a198fb104eecdc0d311b --- develop/upgrade.html | 14 ++++++++++++++ 1 file changed, 14 insertions(+) (limited to 'develop/upgrade.html') diff --git a/develop/upgrade.html b/develop/upgrade.html index 4ea94512f1..2fd643a761 100644 --- a/develop/upgrade.html +++ b/develop/upgrade.html @@ -235,6 +235,20 @@ dpkg -i matrix-synapse-py3_1.3.0+stretch1_amd64.deb

Removal of the generate_short_term_login_token module API method

As announced with the release of Synapse 1.69.0, the deprecated generate_short_term_login_token module method has been removed.

Modules relying on it can instead use the create_login_token method.

+

Changes to the events received by application services (interest)

+

To align with spec (changed in +MSC3905), Synapse now +only considers local users to be interesting. In other words, the users namespace +regex is only be applied against local users of the homeserver.

+

Please note, this probably doesn't affect the expected behavior of your application +service, since an interesting local user in a room still means all messages in the room +(from local or remote users) will still be considered interesting. And matching a room +with the rooms or aliases namespace regex will still consider all events sent in the +room to be interesting to the application service.

+

If one of your application service's users regex was intending to match a remote user, +this will no longer match as you expect. The behavioral mismatch between matching all +local users and some remote users is why the spec was changed/clarified and this +caveat is no longer supported.

Upgrading to v1.69.0

Changes to the receipts replication streams

Synapse now includes information indicating if a receipt applies to a thread when -- cgit 1.5.1