143 posts tagged with "Releases" (See all Category)

Atom Feed

Room Version 6, Client-Server r0.6.1, and Federation r0.1.4 spec releases

27.05.2020 00:00 — Releases Travis Ralston

Room Version 6, Client-Server r0.6.1, and Federation r0.1.4 spec releases

Hey all,

It's been a little while since we've done a spec release, so here we are with Room Version 6, Client-Server r0.6.1, and Federation r0.1.4.

Room Version 6 (and the associated Federation r0.1.4 release) is largely something for implementations to worry about. It contains new event authorisation rules, changes to the redaction algorithm, and stricter compliance for JSON.

Client-Server r0.6.1 contains a number of clarifications as well as SSO support for authorisation, "soft logout" to avoid needlessly destroying e2e history, and new ways to publish aliases within rooms.

If you're wondering where all the E2E-by-default related MSCs are - we're doing final iterations based on the real-world feedback from the E2E-by-default launch a few weeks ago, and they are then expected to land in the upcoming Client-Server r0.7.

Here's all the MSCs that got merged since the last release:

  • MSC2240: Room version 6
  • MSC2457: Invalidating devices during password modification
  • MSC2454: Support UI auth for SSO
  • MSC2451: Remove query_auth federation endpoint
  • MSC2432: Updated semantics for publishing room aliases
  • MSC2324: Facilitating early releases of software dependent on spec
  • MSC2313: Moderation policies as rooms
  • MSC1466: Soft Logout
  • MSC2540: Stricter event validation: JSON compliance
  • MSC2209: Alter auth rules to check notifications in
  • MSC1802: Remove the '200' value from some federation responses

Client-Server r0.6.1 changelog

New Endpoints

  • Added /rooms/{roomId}/aliases for retrieving local aliases for a room. (#2562)

Backwards Compatible Changes

  • Added data structures for defining moderation policies in rooms per MSC2313. (#2434)
  • Optionally invalidate other access tokens during password modification per MSC2457. (#2523)
  • Add User-Interactive Authentication for SSO-backed homeserver per MSC2454. (#2532)
  • Add soft-logout support per MSC1466. (#2546)
  • Replaced legacy room alias handling with a more sustainable solution per MSC2432. (#2562)

Spec Clarifications

  • List available enum values for the room versions capability. (#2245)
  • Fix various spelling errors throughout the specification. (#2351, #2415, #2453, #2524, #2553, #2569)
  • Minor clarifications to token-based User-Interactive Authentication. (#2369)
  • Minor clarification for what the user directory searches. (#2381)
  • Fix key export format example to match the specification. (#2430)
  • Clarify the IV data type for encrypted files. (#2492)
  • Fix the .m.rule.contains_user_name default push rule to set the highlight tweak. (#2519)
  • Clarify that an event_id is returned when sending events. (#2525)
  • Fix some numbers in the specification to match their explanation text. (#2554)
  • Move redaction algorithm into the room version specifications. (#2563)
  • Clarify signature object structures for encryption. (#2566)
  • Clarify which events are created as part of /createRoom. (#2571)
  • Remove claims that the homeserver is exclusively responsible for profile information in membership events. (#2574)

Server-Server (Federation) r0.1.4 changelog

New Endpoints

  • Add new POST /publicRooms endpoint for filtering the room directory. (#2305)
  • Add new v2 /send_join and /send_leave endpoints per MSC1802. (#2547)

Removed Endpoints

Spec Clarifications

  • Move auth event selection to a more obvious location. (#2392)
  • Fix typo in Request Authentication python example. (#2510)
  • Clarify which fields are required on the key server endpoints. (#2527)
  • Clarify the limits of prev_events and auth_events for PDUs. (#2538)
  • Clarify which events are targeted by backfill. (#2559)
  • Fix the response format of the /send endpoint. (#2560)
  • Clarify signature object structures for encryption. (#2566)
  • Clarify the server names to use when signing requests. (#2570)
  • Clarify the state/auth chain requirements for /send_join. (#2575)
  • Fix various spelling errors throughout the specification. (#2577)

Synapse 1.13.0 released

19.05.2020 00:00 — Releases Neil Johnson

Synapse 1.13.0 is here and it's a whopper!

Highlights include new support for User Interactive Authentication (UIA) for Single Sign-on (SSO) installations. This means that for the first time features that require the user to re-authenticate are available for servers that authenticate by SSO. Notably this means that these servers now support cross signing!

SSO admins should take a look at the SSO notes in the changelog.

We have been working hard on performance for large scale installations. Anyone supporting more than a few thousand users is probably running Synapse in worker mode. This means splitting out functionality from the master process and making use of multiple cores (or machines) to spread the load. Cross process communication was previously handled by a home grown TCP based replication protocol. As part of our ongoing efforts to improve performance we have replaced this replication system with Redis and have been running Redis in production on for the past 2 weeks.

Redis itself does not provide a significant performance win directly but it means that it is much less expensive to add new workers to a cluster. The topology of the old system meant that every additional worker carried a small but not insignificant overhead to the master process. Since moving to Redis we have doubled the number of workers backing

We still consider Redis to be experimental and admins should not feel obliged to upgrade. However it looks very promising and we are likely to deprecate the old replication system in future. So watch this space - Redis is the future.

Finally we've seen lots of improvements to our documentation and many thanks for those in the community making contributions in this area.

It is also worth noting for those of you contributing to Synapse that the develop branch is now the default. More details in the changelog, so take a look.

Get 1.13.0 from github or any of the sources mentioned at

Changelog since v1.12.4

Synapse 1.13.0 (2020-05-19)

This release brings some potential changes necessary for certain configurations of Synapse:

  • If your Synapse is configured to use SSO and have a custom sso_redirect_confirm_template_dir configuration option set, you will need to duplicate the new sso_auth_confirm.html, sso_auth_success.html and sso_account_deactivated.html templates into that directory.
  • Synapse plugins using the complete_sso_login method of synapse.module_api.ModuleApi should instead switch to the async/await version, complete_sso_login_async, which includes additional checks. The former version is now deprecated.
  • A bug was introduced in Synapse 1.4.0 which could cause the room directory to be incomplete or empty if Synapse was upgraded directly from v1.2.1 or earlier, to versions between v1.4.0 and v1.12.x.

Please review UPGRADE.rst for more details on these changes and for general upgrade guidance.

Notice of change to the default git branch for Synapse

With the release of Synapse 1.13.0, the default git branch for Synapse has changed to develop, which is the development tip. This is more consistent with common practice and modern git usage.

The master branch, which tracks the latest release, is still available. It is recommended that developers and distributors who have scripts which run builds using the default branch of Synapse should therefore consider pinning their scripts to master.


  • Extend the web_client_location option to accept an absolute URL to use as a redirect. Adds a warning when running the web client on the same hostname as homeserver. Contributed by Martin Milata. (#7006)
  • Set Referrer-Policy header to no-referrer on media downloads. (#7009)
  • Add support for running replication over Redis when using workers. (#7040, #7325, #7352, #7401, #7427, #7439, #7446, #7450, #7454)
  • Admin API POST /_synapse/admin/v1/join/<roomIdOrAlias> to join users to a room like auto_join_rooms for creation of users. (#7051)
  • Add options to prevent users from changing their profile or associated 3PIDs. (#7096)
  • Support SSO in the user interactive authentication workflow. (#7102, #7186, #7279, #7343)
  • Allow server admins to define and enforce a password policy (MSC2000). (#7118)
  • Improve the support for SSO authentication on the login fallback page. (#7152, #7235)
  • Always whitelist the login fallback in the SSO configuration if public_baseurl is set. (#7153)
  • Admin users are no longer required to be in a room to create an alias for it. (#7191)
  • Require admin privileges to enable room encryption by default. This does not affect existing rooms. (#7230)
  • Add a config option for specifying the value of the Accept-Language HTTP header when generating URL previews. (#7265)
  • Allow /requestToken endpoints to hide the existence (or lack thereof) of 3PID associations on the homeserver. (#7315)
  • Add a configuration setting to tweak the threshold for dummy events. (#7422)


  • Don't attempt to use an invalid sqlite config if no database configuration is provided. Contributed by @nekatak. (#6573)
  • Fix single-sign on with CAS systems: pass the same service URL when requesting the CAS ticket and when calling the proxyValidate URL. Contributed by @Naugrimm. (#6634)
  • Fix missing field default when fetching user-defined push rules. (#6639)
  • Improve error responses when accessing remote public room lists. (#6899, #7368)
  • Transfer alias mappings on room upgrade. (#6946)
  • Ensure that a user interactive authentication session is tied to a single request. (#7068, #7455)
  • Fix a bug in the federation API which could cause occasional "Failed to get PDU" errors. (#7089)
  • Return the proper error (M_BAD_ALIAS) when a non-existent canonical alias is provided. (#7109)
  • Fix a bug which meant that groups updates were not correctly replicated between workers. (#7117)
  • Fix starting workers when federation sending not split out. (#7133)
  • Ensure is_verified is a boolean in responses to GET /_matrix/client/r0/room_keys/keys. Also warn the user if they forgot the version query param. (#7150)
  • Fix error page being shown when a custom SAML handler attempted to redirect when processing an auth response. (#7151)
  • Avoid importing sqlite3 when using the postgres backend. Contributed by David Vo. (#7155)
  • Fix excessive CPU usage by prune_old_outbound_device_pokes job. (#7159)
  • Fix a bug which could cause outbound federation traffic to stop working if a client uploaded an incorrect e2e device signature. (#7177)
  • Fix a bug which could cause incorrect 'cyclic dependency' error. (#7178)
  • Fix a bug that could cause a user to be invited to a server notices (aka System Alerts) room without any notice being sent. (#7199)
  • Fix some worker-mode replication handling not being correctly recorded in CPU usage stats. (#7203)
  • Do not allow a deactivated user to login via SSO. (#7240, #7259)
  • Fix --help command-line argument. (#7249)
  • Fix room publish permissions not being checked on room creation. (#7260)
  • Reject unknown session IDs during user interactive authentication instead of silently creating a new session. (#7268)
  • Fix a SQL query introduced in Synapse 1.12.0 which could cause large amounts of logging to the postgres slow-query log. (#7274)
  • Persist user interactive authentication sessions across workers and Synapse restarts. (#7302)
  • Fixed backwards compatibility logic of the first value of trusted_third_party_id_servers being used for, which occurs when the former, deprecated option is set and the latter is not. (#7316)
  • Fix a bug where event updates might not be sent over replication to worker processes after the stream falls behind. (#7337, #7358)
  • Fix bad error handling that would cause Synapse to crash if it's provided with a YAML configuration file that's either empty or doesn't parse into a key-value map. (#7341)
  • Fix incorrect metrics reporting for renew_attestations background task. (#7344)
  • Prevent non-federating rooms from appearing in responses to federated POST /publicRoom requests when a filter was included. (#7367)
  • Fix a bug which would cause the room directory to be incorrectly populated if Synapse was upgraded directly from v1.2.1 or earlier to v1.4.0 or later. Note that this fix does not apply retrospectively; see the upgrade notes for more information. (#7387)
  • Fix bug in EventContext.deserialize. (#7393)
  • Fix a long-standing bug which could cause messages not to be sent over federation, when state events with state keys matching user IDs (such as custom user statuses) were received. (#7376)
  • Restore compatibility with non-compliant clients during the user interactive authentication process, fixing a problem introduced in v1.13.0rc1. (#7483)
  • Hash passwords as early as possible during registration. (#7523)

Improved Documentation

  • Update Debian installation instructions to recommend installing the virtualenv package instead of python3-virtualenv. (#6892)
  • Improve the documentation for database configuration. (#6988)
  • Improve the documentation of application service configuration files. (#7091)
  • Update pre-built package name for FreeBSD. (#7107)
  • Update postgres docs with login troubleshooting information. (#7119)
  • Clean up a bit. (#7141)
  • Add documentation for running a local CAS server for testing. (#7147)
  • Improve by being explicit about public IP recommendation for TURN relaying. (#7167)
  • Fix a small typo in the metrics_flags config option. (#7171)
  • Update the contributed documentation on managing synapse workers with systemd, and bring it into the core distribution. (#7234)
  • Add documentation to the password_providers config option. Add known password provider implementations to docs. (#7238, #7248)
  • Modify suggested nginx reverse proxy configuration to match Synapse's default file upload size. Contributed by @ProCycleDev. (#7251)
  • Documentation of media_storage_providers options updated to avoid misunderstandings. Contributed by Tristan Lins. (#7272)
  • Add documentation on monitoring workers with Prometheus. (#7357)
  • Clarify endpoint usage in the users admin api documentation. (#7361)

Deprecations and Removals

  • Remove nonfunctional captcha_bypass_secret option from homeserver.yaml. (#7137)

Internal Changes

  • Add benchmarks for LruCache. (#6446)
  • Return total number of users and profile attributes in admin users endpoint. Contributed by Awesome Technologies Innovationslabor GmbH. (#6881)
  • Change device list streams to have one row per ID. (#7010)
  • Remove concept of a non-limited stream. (#7011)
  • Move catchup of replication streams logic to worker. (#7024, #7195, #7226, #7239, #7286, #7290, #7318, #7326, #7378, #7421)
  • Convert some of to async/await. (#7110, #7184, #7241)
  • De-duplicate / remove unused REST code for login and auth. (#7115)
  • Convert *StreamRow classes to inner classes. (#7116)
  • Clean up some LoggingContext code. (#7120, #7181, #7183, #7408, #7426)
  • Add explicit instance_id for USER_SYNC commands and remove implicit conn_id usage. (#7128)
  • Refactored the CAS authentication logic to a separate class. (#7136)
  • Run replication streamers on workers. (#7146)
  • Add tests for outbound device pokes. (#7157)
  • Fix device list update stream ids going backward. (#7158)
  • Use stream.current_token() and remove stream_positions(). (#7172)
  • Move client command handling out of TCP protocol. (#7185)
  • Move server command handling out of TCP protocol. (#7187)
  • Fix consistency of HTTP status codes reported in log lines. (#7188)
  • Only run one background database update at a time. (#7190)
  • Remove sent outbound device list pokes from the database. (#7192)
  • Add a background database update job to clear out duplicate device_lists_outbound_pokes. (#7193)
  • Remove some extraneous debugging log lines. (#7207)
  • Add explicit Python build tooling as dependencies for the snapcraft build. (#7213)
  • Add typing information to federation server code. (#7219)
  • Extend room admin api (GET /_synapse/admin/v1/rooms) with additional attributes. (#7225)
  • Unblacklist '/upgrade creates a new room' sytest for workers. (#7228)
  • Remove redundant checks on daemonize from synctl. (#7233)
  • Upgrade jQuery to v3.4.1 on fallback login/registration pages. (#7236)
  • Change log line that told user to implement onLogin/onRegister fallback js functions to a warning, instead of an info, so it's more visible. (#7237)
  • Correct the parameters of a test fixture. Contributed by Isaiah Singletary. (#7243)
  • Convert auth handler to async/await. (#7261)
  • Add some unit tests for replication. (#7278)
  • Improve typing annotations in synapse.replication.tcp.streams.Stream. (#7291)
  • Reduce log verbosity of url cache cleanup tasks. (#7295)
  • Fix sample SAML Service Provider configuration. Contributed by @frcl. (#7300)
  • Fix StreamChangeCache to work with multiple entities changing on the same stream id. (#7303)
  • Fix an incorrect import in IdentityHandler. (#7319)
  • Reduce logging verbosity for successful federation requests. (#7321)
  • Convert some federation handler code to async/await. (#7338)
  • Fix collation for postgres for unit tests. (#7359)
  • Convert RegistrationWorkerStore.is_server_admin and dependent code to async/await. (#7363)
  • Add an instance_name to RDATA and POSITION replication commands. (#7364)
  • Thread through instance name to replication client. (#7369)
  • Convert synapse.server_notices to async/await. (#7394)
  • Convert synapse.notifier to async/await. (#7395)
  • Fix issues with the Python package manifest. (#7404)
  • Prevent methods in synapse.handlers.auth from polling the homeserver config every request. (#7420)
  • Speed up fetching device lists changes when handling /sync requests. (#7423)
  • Run group attestation renewal in series rather than parallel for performance. (#7442)
  • Fix linting errors in new version of Flake8. (#7470)
  • Update the version of dh-virtualenv we use to build debs, and add focal to the list of target distributions. (#7526)

Synapse 1.12.4 released

23.04.2020 19:04 — Releases Neil Johnson

A small patch release containing features and bugs to support the upcoming launch of cross signing. We are very close now :)

Get 1.12.4 from github or any of the sources mentioned at

Changelog since v1.12.3

Synapse 1.12.4 (2020-04-23)

No significant changes.

Synapse 1.12.4rc1 (2020-04-22)


  • Always send users their own device updates. (#7160)
  • Add support for handling GET requests for account_data on a worker. (#7311)


  • Fix a bug that prevented cross-signing with users on worker-mode synapses. (#7255)
  • Do not treat display names as globs in push rules. (#7271)
  • Fix a bug with cross-signing devices belonging to remote users who did not share a room with any user on the local homeserver. (#7289)

Synapse 1.12.2 released

02.04.2020 00:00 — Releases Neil Johnson

A small patch release to fix regressions introduced in v1.11.0 and v1.12.0.

Update 1.12.3 is a fast follow release from 1.12.2

Get 1.12.3 (not 1.12.2) from github or any of the sources mentioned at

Changelog since v1.12.0

Synapse 1.12.3 (2020-04-03)

  • Remove the the pin to Pillow 7.0 which was introduced in Synapse 1.12.2, and correctly fix the issue with building the Debian packages. (#7212)

Synapse 1.12.2 (2020-04-02)

This release fixes an issue with building the debian packages.

Synapse 1.12.1 (2020-04-02)

No significant changes since 1.12.1rc1.

Synapse 1.12.1rc1 (2020-03-31)


  • Fix starting workers when federation sending not split out. (#7133). Introduced in v1.12.0.
  • Avoid importing sqlite3 when using the postgres backend. Contributed by David Vo. (#7155). Introduced in v1.12.0rc1.
  • Fix a bug which could cause outbound federation traffic to stop working if a client uploaded an incorrect e2e device signature. (#7177). Introduced in v1.11.0.

Synapse 1.12.0 released

23.03.2020 00:00 — Releases Neil Johnson

Synapse 1.12.0 is here.

The most important reason to upgrade to 1.12.0 is that it contains performance improvements to boost the efficiency of state resolution in room versions greater than v1 (#7095).

It also contains an implementation of (MSC2432) designed to limit room alias abuse. The MSC contains the full details, but in short admins now have more control over aliases as they appear on their local server.

There is also plenty of ground work for our master process sharding project. Nothing that can be used today unfortunately, but expect big improvements for worker based deployments over the coming weeks.

Please pay special attention to the security advisory in the changelog, TL;DR make sure your installation is using Twisted 20.3.0.

Also, note that once Synapse 1.13.0 is released, the default branch will change to being develop rather than master. Again more details follow in the changelog.

Get the new release from github or any of the sources mentioned at

Changelog since Synapse 1.11.1

Synapse 1.12.0 (2020-03-23)

No significant changes since 1.12.0rc1.

Debian packages and Docker images are rebuilt using the latest versions of dependency libraries, including Twisted 20.3.0. Please see security advisory below.

Security advisory

Synapse may be vulnerable to request-smuggling attacks when it is used with a reverse-proxy. The vulnerabilities are fixed in Twisted 20.3.0, and are described in CVE-2020-10108 and CVE-2020-10109. For a good introduction to this class of request-smuggling attacks, see

We are not aware of these vulnerabilities being exploited in the wild, and do not believe that they are exploitable with current versions of any reverse proxies. Nevertheless, we recommend that all Synapse administrators ensure that they have the latest versions of the Twisted library to ensure that their installation remains secure.

  • Administrators using the Docker image or the Debian/Ubuntu packages from should ensure that they have version 1.12.0 installed: these images include Twisted 20.3.0.
  • Administrators who have installed Synapse from source should upgrade Twisted within their virtualenv by running:
    <path_to_virtualenv>/bin/pip install 'Twisted>=20.3.0'
  • Administrators who have installed Synapse from distribution packages should consult the information from their distributions.

The Synapse instance was not vulnerable to these vulnerabilities.

Advance notice of change to the default git branch for Synapse

Currently, the default git branch for Synapse is master, which tracks the latest release.

After the release of Synapse 1.13.0, we intend to change this default to develop, which is the development tip. This is more consistent with common practice and modern git usage.

Although we try to keep develop in a stable state, there may be occasions where regressions creep in. Developers and distributors who have scripts which run builds using the default branch of Synapse should therefore consider pinning their scripts to master.

Synapse 1.12.0rc1 (2020-03-19)


  • Changes related to room alias management (MSC2432):
    • Publishing/removing a room from the room directory now requires the user to have a power level capable of modifying the canonical alias, instead of the room aliases. (#6965)
    • Validate the alt_aliases property of canonical alias events. (#6971)
    • Users with a power level sufficient to modify the canonical alias of a room can now delete room aliases. (#6986)
    • Implement updated authorization rules and redaction rules for aliases events, from MSC2261 and MSC2432. (#7037)
    • Stop sending events during room creation and upgrade. (#6941)
    • Synapse no longer uses room alias events to calculate room names for push notifications. (#6966)
    • The room list endpoint no longer returns a list of aliases. (#6970)
    • Remove special handling of aliases events from MSC2260 added in v1.10.0rc1. (#7034)
  • Expose the synctl, hash_password and generate_config commands in the snapcraft package. Contributed by @devec0. (#6315)
  • Check that server_name is correctly set before running database updates. (#6982)
  • Break down monthly active users by appservice_id and emit via Prometheus. (#7030)
  • Render a configurable and comprehensible error page if something goes wrong during the SAML2 authentication process. (#7058, #7067)
  • Add an optional parameter to control whether other sessions are logged out when a user's password is modified. (#7085)
  • Add prometheus metrics for the number of active pushers. (#7103, #7106)
  • Improve performance when making HTTPS requests to sygnal, sydent, etc, by sharing the SSL context object between connections. (#7094)


  • When a user's profile is updated via the admin API, also generate a displayname/avatar update for that user in each room. (#6572)
  • Fix a couple of bugs in email configuration handling. (#6962)
  • Fix an issue affecting worker-based deployments where replication would stop working, necessitating a full restart, after joining a large room. (#6967)
  • Fix duplicate key error which was logged when rejoining a room over federation. (#6968)
  • Prevent user from setting 'deactivated' to anything other than a bool on the v2 PUT /users Admin API. (#6990)
  • Fix py35-old CI by using native tox package. (#7018)
  • Fix a bug causing org.matrix.dummy_event to be included in responses from /sync. (#7035)
  • Fix a bug that renders UTF-8 text files incorrectly when loaded from media. Contributed by @TheStranjer. (#7044)
  • Fix a bug that would cause Synapse to respond with an error about event visibility if a client tried to request the state of a room at a given token. (#7066)
  • Repair a data-corruption issue which was introduced in Synapse 1.10, and fixed in Synapse 1.11, and which could cause /sync to return with 404 errors about missing events and unknown rooms. (#7070)
  • Fix a bug causing account validity renewal emails to be sent even if the feature is turned off in some cases. (#7074)

Improved Documentation

  • Updated CentOS8 install instructions. Contributed by Richard Kellner. (#6925)
  • Fix POSTGRES_INITDB_ARGS in the contrib/docker/docker-compose.yml example docker-compose configuration. (#6984)
  • Change date in for last date of getting TLS certificates to November 2019. (#7015)
  • Document that the fallback auth endpoints must be routed to the same worker node as the register endpoints. (#7048)

Deprecations and Removals

  • Remove the unused query_auth federation endpoint per MSC2451. (#7026)

Internal Changes

  • Add type hints to logging/ (#6309)
  • Add some clarifications to in the database schema directory. (#6615)
  • Refactoring work in preparation for changing the event redaction algorithm. (#6874, #6875, #6983, #7003)
  • Improve performance of v2 state resolution for large rooms. (#6952, #7095)
  • Reduce time spent doing GC, by freezing objects on startup. (#6953)
  • Minor performance fixes to get_auth_chain_ids. (#6954)
  • Don't record remote cross-signing keys in the devices table. (#6956)
  • Use flake8-comprehensions to enforce good hygiene of list/set/dict comprehensions. (#6957)
  • Merge worker apps together. (#6964, #7002, #7055, #7104)
  • Remove redundant store_room call from FederationHandler._process_received_pdu. (#6979)
  • Update warning for incorrect database collation/ctype to include link to documentation. (#6985)
  • Add some type annotations to the database storage classes. (#6987)
  • Port synapse.handlers.presence to async/await. (#6991, #7019)
  • Add some type annotations to the federation base & client classes. (#6995)
  • Port to async/await. (#7020)
  • Add a type check to is_verified when processing room keys. (#7045)
  • Add type annotations and comments to the auth handler. (#7063)

Synapse 1.11.1 released

03.03.2020 00:00 — Releases Neil Johnson

Synapse 1.11.1 is a security release which contains a fix impacting installations using Single Sign-On (i.e. SAML2 or CAS) for authentication. Administrators of such installations are encouraged to upgrade as soon as possible.

Admins not using Single Sign-On to authenticate users are not affected though may wish to upgrade anyway to pull in some unrelated bug fixes.

Thanks to Rhys Davies for the responsible disclosure.

Get the new release from github or any of the sources mentioned at

Changelog since Synapse 1.11.0

Synapse 1.11.1 (2020-03-03)

This release includes a security fix impacting installations using Single Sign-On (i.e. SAML2 or CAS) for authentication. Administrators of such installations are encouraged to upgrade as soon as possible.

The release also includes fixes for a couple of other bugs.


  • Add a confirmation step to the SSO login flow before redirecting users to the redirect URL. (b2bd54a2, 65c73cdf, a0178df1)
  • Fixed set a user as an admin with the admin API PUT /_synapse/admin/v2/users/<user_id>. Contributed by @dklimpel. (#6910)
  • Fix bug introduced in Synapse 1.11.0 which sometimes caused errors when joining rooms over federation, with 'coroutine' object has no attribute 'event_id'. (#6996)

Synapse 1.9.1 released

28.01.2020 00:00 — Releases Neil Johnson

A quick bug fix release that affects admins making use of monthly active user limits. You will know if you are affected because 1.9.0 will not start up. Apologies if you were bitten by this one!

Get the new release from github or any of the sources mentioned at

Changelog since Synapse 1.9.1

Synapse 1.9.1 (2020-01-28)


  • Fix bug where setting mau_limit_reserved_threepids config would cause Synapse to refuse to start. (#6793)

Synapse 1.9.0 released

23.01.2020 00:00 — Releases Neil Johnson

Synapse 1.9.0 contains a bunch of new admin APIs as well as bug fixes to existing ones. In particular we have a new end point that allows admins to query which rooms their server participates in.

Aside from that it is worth noting that we have officially dropped support for SQLite versions < 3.11. Though more generally we would recommend that all admins migrate to Postgres for anything other than test and evaluation purposes.

Get the new release from github or any of the sources mentioned at

Changelog since Synapse 1.8.0

Synapse 1.9.0 (2020-01-23)

WARNING: As of this release, Synapse no longer supports versions of SQLite before 3.11, and will refuse to start when configured to use an older version. Administrators are recommended to migrate their database to Postgres (see instructions here).

If your Synapse deployment uses workers, note that the reverse-proxy configurations for the, and workers have changed, with the addition of a few paths (see the updated configurations here). Existing configurations will continue to work.

Improved Documentation

  • Fix endpoint documentation for the List Rooms admin API. (#6770)

Synapse 1.9.0rc1 (2020-01-22)


  • Allow admin to create or modify a user. Contributed by Awesome Technologies Innovationslabor GmbH. (#5742)
  • Add new quarantine media admin APIs to quarantine by media ID or by user who uploaded the media. (#6681, #6756)
  • Add org.matrix.e2e_cross_signing to unstable_features in /versions as per MSC1756. (#6712)
  • Add a new admin API to list and filter rooms on the server. (#6720)


  • Correctly proxy HTTP errors due to API calls to remote group servers. (#6654)
  • Fix media repo admin APIs when using a media worker. (#6664)
  • Fix "CRITICAL" errors being logged when a request is received for a uri containing non-ascii characters. (#6682)
  • Fix a bug where we would assign a numeric user ID if somebody tried registering with an empty username. (#6690)
  • Fix purge_room admin API. (#6711)
  • Fix a bug causing Synapse to not always purge quiet rooms with a low max_lifetime in their message retention policies when running the automated purge jobs. (#6714)
  • Fix the synapse_port_db not correctly running background updates. Thanks @tadzik for reporting. (#6718)
  • Fix changing password via user admin API. (#6730)
  • Fix /events/:event_id deprecated API. (#6731)
  • Fix monthly active user limiting support for worker mode, fixes #4639. (#6742)
  • Fix bug when setting account_validity to an empty block in the config. Thanks to @Sorunome for reporting. (#6747)
  • Fix AttributeError: 'NoneType' object has no attribute 'get' in hash_password when configuration has an empty password_config. Contributed by @ivilata. (#6753)
  • Fix the docker-compose.yaml overriding the entire /etc folder of the container. Contributed by Fabian Meyer. (#6656)

Improved Documentation

  • Fix a typo in the configuration example for purge jobs in the sample configuration file. (#6621)
  • Add complete documentation of the message retention policies support. (#6624, #6665)
  • Add some helpful tips about changelog entries to the GitHub pull request template. (#6663)
  • Clarify the account_validity and email sections of the sample configuration. (#6685)
  • Add more endpoints to the documentation for Synapse workers. (#6698)

Deprecations and Removals

  • Synapse no longer supports versions of SQLite before 3.11, and will refuse to start when configured to use an older version. Administrators are recommended to migrate their database to Postgres (see instructions here). (#6675)

Internal Changes

  • Add local_current_membership table for tracking local user membership state in rooms. (#6655, #6728)
  • Port synapse.replication.tcp to async/await. (#6666)
  • Fixup synapse.replication to pass mypy checks. (#6667)
  • Allow additional_resources to implement IResource directly. (#6686)
  • Allow REST endpoint implementations to raise a RedirectException, which will redirect the user's browser to a given location. (#6687)
  • Updates and extensions to the module API. (#6688)
  • Updates to the SAML mapping provider API. (#6689, #6723)
  • Remove redundant RegistrationError class. (#6691)
  • Don't block processing of incoming EDUs behind processing PDUs in the same transaction. (#6697)
  • Remove duplicate check for the session query parameter on the /auth/xxx/fallback/web Client-Server endpoint. (#6702)
  • Attempt to retry sending a transaction when we detect a remote server has come back online, rather than waiting for a transaction to be triggered by new data. (#6706)
  • Add StateMap type alias to simplify types. (#6715)
  • Add a DeltaState to track changes to be made to current state during event persistence. (#6716)
  • Add more logging around message retention policies support. (#6717)
  • When processing a SAML response, log the assertions for easier configuration. (#6724)
  • Fixup to pass mypy. (#6732, #6764)
  • Fixup synapse.api to pass mypy. (#6733)
  • Allow streaming cache 'invalidate all' to workers. (#6749)
  • Remove unused CI docker compose files. (#6754)

Synapse 1.8.0 released

09.01.2020 00:00 — Releases Neil Johnson

Synapse 1.8.0 has arrived, it contains a whole host of bug fixes and tweaks, most notably fixing some long standing problems with search.

More generally we are spending a lot of time improving the e2ee experience ahead of switching on e2ee by default, so watch this space.

Get the new release from github or any of the sources mentioned at

Synapse 1.8.0 (2020-01-09)


  • Fix GET request on /_synapse/admin/v2/users endpoint. Contributed by Awesome Technologies Innovationslabor GmbH. (#6563)
  • Fix incorrect signing of responses from the key server implementation. (#6657)

Synapse 1.8.0rc1 (2020-01-07)


  • Add v2 APIs for the send_join and send_leave federation endpoints (as described in MSC1802). (#6349)
  • Add a develop script to generate full SQL schemas. (#6394)
  • Add custom SAML username mapping functionality through an external provider plugin. (#6411)
  • Automatically delete empty groups/communities. (#6453)
  • Add option limit_profile_requests_to_users_who_share_rooms to prevent requirement of a local user sharing a room with another user to query their profile information. (#6523)
  • Add an export_signing_key script to extract the public part of signing keys when rotating them. (#6546)
  • Add experimental config option to specify multiple databases. (#6580)
  • Raise an error if someone tries to use the log_file config option. (#6626)


  • Prevent redacted events from being returned during message search. (#6377, #6522)
  • Prevent error on trying to search a upgraded room when the server is not in the predecessor room. (#6385)
  • Improve performance of looking up cross-signing keys. (#6486)
  • Fix race which occasionally caused deleted devices to reappear. (#6514)
  • Fix missing row in device_max_stream_id that could cause unable to decrypt errors after server restart. (#6555)
  • Fix a bug which meant that we did not send systemd notifications on startup if acme was enabled. (#6571)
  • Fix exception when fetching the key. (#6625)
  • Fix bug where a moderator upgraded a room and became an admin in the new room. (#6633)
  • Fix an error which was thrown by the PresenceHandler _on_shutdown handler. (#6640)
  • Fix exceptions in the synchrotron worker log when events are rejected. (#6645)
  • Ensure that upgraded rooms are removed from the directory. (#6648)
  • Fix a bug causing Synapse not to fetch missing events when it believes it has every event in the room. (#6652)

Improved Documentation

Deprecations and Removals

  • Remove redundant code from event authorisation implementation. (#6502)
  • Remove unused, undocumented /_matrix/content API. (#6628)

Internal Changes

  • Add experimental support for multiple physical databases and split out state storage to separate data store. (#6245, #6510, #6511, #6513, #6564, #6565)
  • Port sections of code base to async/await. (#6496, #6504, #6505, #6517, #6559, #6647, #6653)
  • Remove SnapshotCache in favour of ResponseCache. (#6506)
  • Silence mypy errors for files outside those specified. (#6512)
  • Clean up some logging when handling incoming events over federation. (#6515)
  • Test more folders against mypy. (#6534)
  • Update mypy to new version. (#6537)
  • Adjust the sytest blacklist for worker mode. (#6538)
  • Remove unused get_pagination_rows methods from EventSource classes. (#6557)
  • Clean up logs from the push notifier at startup. (#6558)
  • Improve diagnostics on database upgrade failure. (#6570)
  • Reduce the reconnect time when worker replication fails, to make it easier to catch up. (#6617)
  • Simplify http handling by removing redundant SynapseRequestFactory. (#6619)
  • Add a workaround for synapse raising exceptions when fetching the notary's own key from the notary. (#6620)
  • Automate generation of the sample log config. (#6627)
  • Simplify event creation code by removing redundant queries on the event_reference_hashes table. (#6629)
  • Fix errors when frozen_dicts are enabled. (#6642)

Get the new release from github or any of the sources mentioned at

Synapse 1.7.3 released

31.12.2019 00:00 — Releases Matthew Hodgson

Hi all,

We've just released Synapse 1.7.3 - an important bug fix to address a class of failures due to malformed events. We've seen this in the wild over the last few days, so we'd recommend updating as soon as possible, especially if you are having problems federating.

Get the new release from github or any of the sources mentioned at

The changelog since 1.7.2 is:

Synapse 1.7.3 (2019-12-31)

This release fixes a long-standing bug in the state resolution algorithm.


  • Fix exceptions caused by state resolution choking on malformed events. (#6608)