From 25eebe534e5fd4fe5ecd2947dde386549c3313ec Mon Sep 17 00:00:00 2001 From: erikjohnston Date: Tue, 31 May 2022 13:48:55 +0000 Subject: deploy: 3594f6c1f340f12bfcb2fec9e99ac108a714b508 --- develop/upgrade.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'develop/upgrade.html') diff --git a/develop/upgrade.html b/develop/upgrade.html index 81eb4ce480..779c77129a 100644 --- a/develop/upgrade.html +++ b/develop/upgrade.html @@ -295,9 +295,9 @@ COMMIT;

This comment on issue 11779 has queries that can be used to check a database for this problem in advance.

-

SpamChecker API's check_event_for_spam has a new signature.

+

New signature for the spam checker callback check_event_for_spam

The previous signature has been deprecated.

-

Whereas check_event_for_spam callbacks used to return Union[str, bool], they should now return Union["synapse.module_api.Allow", "synapse.module_api.errors.Codes"].

+

Whereas check_event_for_spam callbacks used to return Union[str, bool], they should now return Union["synapse.module_api.NOT_SPAM", "synapse.module_api.errors.Codes"].

This is part of an ongoing refactoring of the SpamChecker API to make it less ambiguous and more powerful.

If your module implements check_event_for_spam as follows:

async def check_event_for_spam(event):
@@ -313,8 +313,8 @@ has queries that can be used to check a database for this problem in advance.

Upgrading to v1.59.0

Device name lookup over federation has been disabled by default

-- cgit 1.4.1