only validate canonical aliases that are new

Previously we required every alias in a canonical alias event sent by a
client to be valid, and would only validate local aliases. This
prevented clients from adding/removing canonical aliases if there were
existing remote or invalid aliases.
This commit is contained in:
Olivia Lee 2025-01-20 15:46:36 -08:00
parent 50c1e77cd6
commit 29d8fbaefa
No known key found for this signature in database
GPG key ID: 54D568A15B9CD1F9
2 changed files with 59 additions and 12 deletions

View file

@ -228,6 +228,10 @@ This will be the first release of Grapevine since it was forked from Conduit
26. Validate schema of new `m.room.canonical_alias` event sent by clients,
rather than silently allowing any contents if the event can't be parsed.
([!158](https://gitlab.computer.surgery/matrix/grapevine/-/merge_requests/158))
27. Only validate canonical aliases that are new, rather than rather than
revalidating every alias. This makes it possible to add/remove aliases when
some of the existing aliases cannot be validated.
([!158](https://gitlab.computer.surgery/matrix/grapevine/-/merge_requests/158))
### Added