9128 commits

Author	SHA1	Message	Date
Mathieu Velten	d372ab3280	Add cancel_task API to the task scheduler (#19310) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2026-01-08 18:21:24 +00:00
Eric Eastwood	ace2614fad	Remove docs on dead legacy metric names (#19341) ... These metrics were [removed completely from the codebase](444bc56cda/docs/changelogs/CHANGES-2022.md (synapse-1730-2022-12-06)) in Synapse v1.73.0 (2022-12-06). 3-years is plenty enough time ⏩ The deprecation/removal is still in our [upgrade notes](444bc56cda/docs/upgrade.md (deprecation-of-legacy-prometheus-metric-names)) which points to a durable versioned link with the info still available: https://element-hq.github.io/synapse/v1.69/metrics-howto.html#renaming-of-metrics--deprecation-of-old-names-in-12	2026-01-08 10:03:15 -06:00
Andrew Morgan	1db2302303	Bump mdbook from 0.4.17 -> 0.5.2 and remove custom table-of-contents plugin (#19356)	2026-01-07 18:46:03 +00:00
Lukas Tautz	8ff1960878	Fix: use correct parameter when calling get_local_current_membership_for_user_in_room (#19353) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2026-01-07 18:32:16 +00:00
Devon Hudson	cbc5469113	Merge branch 'release-v1.145' into develop	2026-01-07 10:34:01 -07:00
Kierre	7ea78671a3	Drop support for Ubuntu 25.04 'Plucky Puffin', add support for Ubuntu 25.10 'Questing Quokka' (#19348) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2026-01-07 14:10:25 +00:00
Hugh Nimmo-Smith	4dcf113bff	Support for stable m.oauth UIA stage for MSC4312 (#19273)	2026-01-07 12:52:21 +00:00
Patrice Brend'amour	a094d922c9	Implement synapse issue #16751: Treat local_media_directory as optional storage provider (#19204)	2026-01-06 23:29:58 +00:00
Devon Hudson	16bc8c78ba	Update changelog after reverting PR	2026-01-06 14:49:09 -07:00
Devon Hudson	6ac61e4be4	Revert "Add an Admin API endpoint for listing quarantined media (#19268)" (#19351) ... Fixes #19349 This reverts commit 3f636386a6 (https://github.com/element-hq/synapse/pull/19268) as the DB migration was taking too long and blocking media access while it happened. See https://github.com/element-hq/synapse/issues/19349 for further information. ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Travis Ralston <travpc@gmail.com>	2026-01-06 14:46:58 -07:00
Devon Hudson	987b61a92b	Revert "Add an Admin API endpoint for listing quarantined media (#19268)" (#19351) ... Fixes #19349 This reverts commit 3f636386a6 (https://github.com/element-hq/synapse/pull/19268) as the DB migration was taking too long and blocking media access while it happened. See https://github.com/element-hq/synapse/issues/19349 for further information. ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Travis Ralston <travpc@gmail.com>	2026-01-06 21:37:23 +00:00
Tulir Asokan	ac6463c6da	Fix media creation being ratelimited for appservices (#19335) ... Co-authored-by: Andrew Morgan <andrew@amorgan.xyz>	2026-01-06 17:34:38 +00:00
Andrew Morgan	1500733f4a	Replace usage of deprecated assertEquals with assertEqual (#19345)	2026-01-06 17:30:21 +00:00
Devon Hudson	39f80296c5	1.145.0rc1	2026-01-06 09:38:44 -07:00
Olivier 'reivilibre	cd252db3f5	Transform events with client metadata before serialising in /event response. (#19340) ... Fix /event/ endpoint not transforming event with per-requester metadata Pass notif_event through filter_events_for_client \ Not aware of an actual issue here, but seems silly to bypass it Call it filter_and_transform_events_for_client to make it more obvious --------- Signed-off-by: Olivier 'reivilibre <oliverw@matrix.org>	2026-01-06 15:53:13 +00:00
Mathieu Velten	444bc56cda	Add rate limit conf to user directory endpoint (#19291) ... The goal is to avoid that an user could scrape the user directory too quickly.	2026-01-05 13:35:11 -06:00
Eric Eastwood	803e4b4d88	Make it more clear how shared_extra_conf is combined in our Docker configuration scripts (#19323) ... For reference, this PR used to include this whole `shared_config` block in the diff. But https://github.com/element-hq/synapse/pull/19324 was merged first which introduced parts of it already. Here is what this code used to look like: 566670c363/docker/configure_workers_and_start.py (L865-L868) --- Original context for why it was changed this way: https://github.com/matrix-org/synapse/pull/14921#discussion_r1126257933 Previously, this code made me question two things: 1. Do we actually use `worker_config["shared_extra_conf"]` in the templates? - At first glance, I couldn't see why we're updating `shared_extra_conf` here. It's not used in the `worker.yaml.j2` template so all of this seemed a bit pointless. - Turns out, updating `shared_extra_conf` itself is pointless and it's being done as a convenient place to mix the objects to get things right in `shared_config` (confusing). 1. Does it actually do anything? - Because `shared_config` starts out as an empty object, my first glance made me think we we're just updating with an empty object and then just re-assigning. But because we're in a loop, we actually accumulate the `shared_extra_conf` from each worker. I'm not sure whether I'm capturing my confusion well enough here but basically, this made me spend time trying to figure out what/why we're doing things this way and we can use a more clear pattern to accomplish the same thing. --- This change is spawning from looking at the `docker/configure_workers_and_start.py` script in order to add a metrics listener ([upcoming PR](https://github.com/element-hq/synapse/pull/19324)).	2026-01-02 12:08:37 -06:00
Eric Eastwood	9dae6cc595	Add a way to expose metrics from the Docker image (SYNAPSE_ENABLE_METRICS) (#19324) ... Spawning from wanting to [run a load test](https://github.com/element-hq/synapse-rust-apps/pull/397) against the Complement Docker image of Synapse and see metrics from the homeserver. ### Why not just provide your own homeserver config? Probably possible but it gets tricky when you try to use the workers variant of the Docker image (`docker/Dockerfile-workers`). The way to workaround it would probably be to `yq` edit everything in a script and change `/data/homeserver.yaml` and `/conf/workers/*.yaml` to add the `metrics` listener. And then modify `/conf/workers/shared.yaml` to add `enable_metrics: true`. Doesn't spark much joy.	2026-01-01 14:00:00 -06:00
Eric Eastwood	bd94152e06	Stream Complement progress and format logs in a separate step after all tests are done (#19326) ... This way we can see what's happening as the tests run instead of nothing until the end. Also useful to split the test output from the formatting so we can take the raw test output before formatting gobbles it all up. Same thing I did in https://github.com/element-hq/synapse-rust-apps/pull/361	2025-12-31 14:43:04 -06:00
Eric Eastwood	7a24fafbc3	Auto-formatting .github/workflows/tests.yml from VSCode (#19327)	2025-12-29 12:20:58 -06:00
Eric Eastwood	41938d6fd2	Log the original bind exception when encountering Failed to listen on 0.0.0.0, continuing because listening on [::] (#19297) ... **Before:** ``` WARNING - call_when_running - Failed to listen on 0.0.0.0, continuing because listening on [::] ``` **After:** ``` WARNING - call_when_running - Failed to listen on 0.0.0.0, continuing because listening on [::]. Original exception: CannotListenError: Couldn't listen on 0.0.0.0:8008: [Errno 98] Address already in use. ```	2025-12-19 14:29:04 -06:00
Andrew Ferrazzutti	f4320b5a49	Admin API: worker support for Query User Account (#19281)	2025-12-16 17:42:08 +00:00
Tulir Asokan	3989d22a37	Implement pagination for MSC2666 (#19279) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2025-12-16 15:24:36 +00:00
Joshua Goins	0395b71e25	Fix Mastodon URL previews not showing anything useful (#19231) ... Fixes #18444. Inside of UrlPreviewer, we need to combine two dicts (one from oEmbed, and one from OpenGraph metadata in the HTML) and in Mastodon's case they were very different. Single Page Applications (SPAs) seem to sometimes provide better information in the OpenGraph tags than the oEmbed stubs, because the oEmbed stubs are filled in with JavaScript that Synapse does not execute. This change improves previews on Mastodon and YouTube (for the same reason). Tested to not regress previews of Twitter or GitHub.	2025-12-16 13:02:29 +00:00
Denis Kasak	29fd0116a5	Improve proxy support for the federation_client.py dev script (#19300) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2025-12-16 11:06:07 +00:00
Travis Ralston	0f2b29511f	Allow admins to bypass the quarantine check on media downloads (#19275) ... Co-authored-by: turt2live <1190097+turt2live@users.noreply.github.com> Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2025-12-15 17:23:33 +00:00
Andre Klärner	466994743a	Document importance of public_baseurl for delegation and OIDC (#19270) ... I just stumbled across the fact that my config used delegation as recommended by the docs, and hosted Synapse on a subdomain. However my config never had `public_baseurl` set and worked without issues, until I just now tried to setup OIDC. OIDC is initialized by the client instructing to open a URL on the homeserver, and initially the correct URL is called, but Synapse does not recognize it without `public_baseurl` being set correctly. After changing this it immediately started working. So in order to prevent anybody from making the same mistake, this adds a small clarifying block in the OIDC docs.	2025-12-12 18:07:39 -06:00
Devon Hudson	df24e0f302	Fix support for older versions of zope-interface (#19274) ... Fixes #19269 Versions of zope-interface from RHEL, Ubuntu LTS 22 & 24 and OpenSuse don't support the new python union `X | Y` syntax for interfaces. This PR partially reverts the change over to fully use the new syntax, adds a minimum supported version of zope-interface to Synapse's dependency list, and removes the linter auto-upgrades which prefer the newer syntax. ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2025-12-12 15:34:13 +00:00
Mathieu Velten	7347cc436e	Add memberships admin API (#19260) ... Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2025-12-12 13:35:46 +00:00
Travis Ralston	3f636386a6	Add an Admin API endpoint for listing quarantined media (#19268) ... Co-authored-by: turt2live <1190097+turt2live@users.noreply.github.com> Co-authored-by: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>	2025-12-12 13:30:21 +00:00
Andrew Morgan	1f7f16477d	Unpin Rust from 1.82.0 (#19302)	2025-12-12 11:31:55 +00:00
Erik Johnston	dfd00a986f	Fix sliding sync performance slow down for long lived connections. (#19206) ... Fixes https://github.com/element-hq/synapse/issues/19175 This PR moves tracking of what lazy loaded membership we've sent to each room out of the required state table. This avoids that table from continuously growing, which massively helps performance as we pull out all matching rows for the connection when we receive a request. The new table is only read when we have data in a room to send, so we end up reading a lot fewer rows from the DB. Though we now read from that table for every room we have events to return in, rather than once at the start of the request. For an explanation of how the new table works, see the [comment](https://github.com/element-hq/synapse/blob/erikj/sss_better_membership_storage2/synapse/storage/schema/main/delta/93/02_sliding_sync_members.sql#L15-L38) on the table schema. The table is designed so that we can later prune old entries if we wish, but that is not implemented in this PR. Reviewable commit-by-commit. --------- Co-authored-by: Eric Eastwood <erice@element.io>	2025-12-12 10:02:57 +00:00
Devon Hudson	cdf286d405	Use uv to test full set of minimum deps in CI (#19289) ... Stemming from #19274 this updates the `olddeps` CI to test against not just the minimum version of our explicit dependencies, but also the minimum version of all implicit (transitive) dependencies that are pulled in from the explicit dependencies themselves. ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters))	2025-12-11 17:58:27 +00:00
Andrew Morgan	3aaa2e80b2	Switch the build backend from poetry-core to maturin (#19234)	2025-12-10 14:46:47 +00:00
Devon Hudson	8b0083cad9	Respond with useful error codes when Content-Length header/s are invalid (#19212) ... Related to https://github.com/element-hq/synapse/issues/17035, when Synapse receives a request that is larger than the maximum size allowed, it aborts the connection without ever sending back a HTTP response. I dug into our usage of twisted and how best to try and report such an error and this is what I came up with. It would be ideal to be able to report the status from within `handleContentChunk` but that is called too early on in the twisted http handling code, before things have been setup enough to be able to properly write a response. I tested this change out locally (both with C-S and S-S apis) and they do receive a 413 response now in addition to the connection being closed. Hopefully this will aid in being able to quickly detect when https://github.com/element-hq/synapse/issues/17035 is occurring as the current situation makes it very hard to narrow things down to that specific issue without making a lot of assumptions. This PR also responds with more meaningful error codes now in the case of: - multiple `Content-Length` headers - invalid `Content-Length` header value - request content size being larger than the `Content-Length` value ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Eric Eastwood <erice@element.io>	2025-12-08 21:39:18 +00:00
Andrew Morgan	a096fba969	Group non-breaking dependabot PRs together to reduce review load (#18402)	2025-12-05 10:48:01 +00:00
Devon Hudson	e8710e7c5e	Don't include debug logs in Clock unless explicitly enabled (#19278) ... Fixes #19276 This log with stack traces results in a ton of noise in the logs and is confusing to users since it looks like it's an error in the logs. This PR removes the stack trace from the log. This can be re-enabled on demand if it is deemed necessary in the future. ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters))	2025-12-04 23:49:24 +00:00
Devon Hudson	978ae0b080	Merge branch 'release-v1.144' into develop	2025-12-02 15:06:23 -07:00
Devon Hudson	989c4d2585	Update changelog	2025-12-02 13:11:50 -07:00
Devon Hudson	4cd05baaec	Fix bug where Duration was logged incorrectly (#19267) ... ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters))	2025-12-02 13:09:44 -07:00
Devon Hudson	d688daf41c	Fix bug where Duration was logged incorrectly (#19267) ... ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters))	2025-12-02 20:08:32 +00:00
Eric Eastwood	83023ce1e0	Be able to shutdown homeserver that failed to start (#19232) ... For example, a homeserver can fail to `start` if the port is already in use or the port number is invalid (not 0-65535) Fix https://github.com/element-hq/synapse/issues/19189 Follow-up to https://github.com/element-hq/synapse/pull/18828 ### Background As part of Element's plan to support a light form of vhosting (virtual host) (multiple instances of Synapse in the same Python process) (c.f [Synapse Pro for small hosts](https://docs.element.io/latest/element-server-suite-pro/synapse-pro-for-small-hosts/overview/)), we're currently diving into the details and implications of running multiple instances of Synapse in the same Python process. "Clean tenant deprovisioning" tracked internally by https://github.com/element-hq/synapse-small-hosts/issues/50	2025-12-02 11:28:46 -06:00
Eric Eastwood	39316672da	Be able to shutdown homeserver that hasn't setup (#19187) ... For example, a homeserver can fail to `setup` if it fails to connect to the database. Fix https://github.com/element-hq/synapse/issues/19188 Follow-up to https://github.com/element-hq/synapse/pull/18828 ### Background As part of Element's plan to support a light form of vhosting (virtual host) (multiple instances of Synapse in the same Python process) (c.f Synapse Pro for small hosts), we're currently diving into the details and implications of running multiple instances of Synapse in the same Python process. "Clean tenant deprovisioning" tracked internally by https://github.com/element-hq/synapse-small-hosts/issues/50	2025-12-02 10:58:06 -06:00
Andrew Morgan	f86918e562	Remove the currently broken netlify GHA workflow (#19262)	2025-12-02 16:46:08 +00:00
Andrew Morgan	3d28e2213f	Dependabot: allow 10 open PRs for general updates (#19253)	2025-12-02 16:45:54 +00:00
Andrew Morgan	0dfc21ca9f	Remove "Updates to locked dependencies" section from changelog (#19254)	2025-12-02 16:45:41 +00:00
Andrew Morgan	ffd0b4c079	Add a 14-day cooldown for dependency updates (#19258)	2025-12-02 16:45:28 +00:00
Devon Hudson	5fe4b7ed60	1.144.0rc1	2025-12-02 09:21:08 -07:00
Devon Hudson	2862c77837	Remove macos wheels from CI (#19263) ... Follows #19225 and stops building macos wheels in CI. ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters))	2025-12-02 15:59:27 +00:00
Erik Johnston	022e56cce3	Move security note from README into the docs (#19259) ... This is a) to simplify the README and b) so that we can easily link to the security page from e.g. the installation guide. Follows on from https://github.com/element-hq/synapse/pull/19228	2025-12-02 14:25:12 +00:00