grapevine/book
Olivia Lee a34bca3986
transfer local canonical aliases to new room on upgrade
When upgrading rooms, we reassign any local aliases from the old room to
the new room. This commit updates the m.room.canonical_alias events in
the old and new rooms to reflect which aliases were moved. The spec is
unclear on whether the server should do this[1], but it's consistent
with synapse's behavior.

I went with putting the canonical alias update logic inline, rather than
something like add_canonical_alias and remove_canonical_alias helper
functions to the alias service, because it's desirable to have the alias
updates be sent as a single event than a separate event for each change.

[1]: https://github.com/matrix-org/matrix-spec/issues/2142
2025-05-18 14:13:41 -07:00
..
contributing add a style guide 2024-12-11 14:01:38 -08:00
installing document that conduwuit migration is unlikely to work 2025-04-11 13:10:23 -07:00
changelog.md transfer local canonical aliases to new room on upgrade 2025-05-18 14:13:41 -07:00
code-of-conduct.md add a code of conduct 2024-06-17 16:39:22 -07:00
contributing.md move security info to its own page 2024-12-11 13:26:16 -08:00
installing.md document supported targets 2024-12-13 16:59:13 -08:00
introduction.md rearrange introduction 2024-12-13 17:00:37 -08:00
migration.md move conduit migration to installing section 2024-12-13 16:59:13 -08:00
SUMMARY.md document that conduwuit migration is unlikely to work 2025-04-11 13:10:23 -07:00