NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #3198 by repository stars
Latest stable
v0.99.19
Last release 1 years ago
17 Nov 2025
Ships unpredictably
gaps range from 9 days to 1.2 years
Nearly every release is documented
notes for 22 of 22 stable releases
Nothing withdrawn
no release was ever pulled
4 years old
147 releases · first in 2022
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fix a critical issue which can cause undecryptable messages if the server admin drops/deletes the sliding sync proxy database. This would not only los
extra_well_known_client_content in homeserver.yaml by @jessebot in https://github.com/matrix-org/sliding-sync/pull/443Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.18...v0.99.19
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Startup times are reduced by around 20-40% by utilising magical postgres queries over SELECT DISTINCT.
SELECT DISTINCT.since param in sync v2 is URL encoded.Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.17...v0.99.18
Nothing published for this version
Nothing published for this version
Nothing published for this version
As of this version, docker images are now signed.
As of this version, docker images are now signed.
Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.16...v0.99.17
Nothing published for this version
Implement MSC4102 which fixes a bug around threaded read receipts which could cause a room to appear as permanently unread.
timeline_limit.README.md doc by @maxkratz in https://github.com/matrix-org/sliding-sync/pull/395Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.15...v0.99.16
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Fixed an issue which would cause metadata about a space child room to be erroneously sent to active connections, even if they weren't in the room. Thi
/hierarchy endpoint. This would appear in Element X as a new room in the room list with a room name and avatar, but no timeline history. Restarting Element X would remove the room.avatar field would be set to the other user even if the room was not a DM room.Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.14...v0.99.15
Fixed a bug which prevented fallback key consumption from being correctly relayed to clients. For some clients (Element X) this would also cause a fal
Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.13...v0.99.14
Add the ability to connect to the upstream homeserver and listen for sliding sync connections over Unix sockets. (By @cyberb, https://github.com/matri
Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.12...v0.99.13
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Docker images available at: https://github.com/matrix-org/sliding-sync/pkgs/container/sliding-sync
Docker images available at: https://github.com/matrix-org/sliding-sync/pkgs/container/sliding-sync
timeline_limit) then the server could return an incorrect timeline, omitting events they had permission to see and returning a prev_batch token which would not recover those events.?timeout= be hit naturally.v* tags too. by @DMRobertson in https://github.com/matrix-org/sliding-sync/pull/341Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.11...v0.99.12
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Docker images available at: https://github.com/matrix-org/sliding-sync/pkgs/container/sliding-sync
Docker images available at: https://github.com/matrix-org/sliding-sync/pkgs/container/sliding-sync
SYNCV3_DB_IDLE_TIMEOUT_SECS. On shared infrastructure where database connections are at a premium, a low idle timeout can be used to reap connections rapidly. On dedicated infrastructure where the database is just used for sliding sync, a high idle timeout can slightly improve performance when communicating with the database.include_heroes: true. See MSC3575 for precise notation.SYNCV3_HTTP_TIMEOUT_SECS and associated SYNCV3_HTTP_INITIAL_TIMEOUT_SECS, which configures the timeouts for sync v2 pollers. A high timeout is essential for large accounts, where initial sync v2 requests may take 10s of minutes. A lower timeout can be beneficial when network connectivity is interrupted. Having a large timeout (e.g 30min) may mean it can take up to 30 minutes for the proxy to realise that a sync v2 request has failed, during which time the device has not received any data. The proxy defaults to 30 minutes initial and 5 minutes otherwise. If network connectivity between the proxy and upstream homeserver is particularly poor, you may want to lower SYNCV3_HTTP_TIMEOUT_SECS.room.name with the new calculated name.SYNCV3_SERVER cannot be reached at startup, log a warning. This should help to reduce configuration errors./metrics collectors when under heavy load, due to it being a high cardinality metric. This could cause /metrics responses to be extremly large, enough to cause the collector to refuse to process the response, causing gaps in metrics collection.RequestedLatestEvents field from UserRoomData by @DMRobertson in https://github.com/matrix-org/sliding-sync/pull/324Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.10...v0.99.11
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
bugfix: set unsigned.redacted_because field on redaction by @kegsay in https://github.com/matrix-org/sliding-sync/pull/291
Bug fixes:
unsigned.redacted_because field on redaction by @kegsay in https://github.com/matrix-org/sliding-sync/pull/291Improvements:
set_presence=offline to reduce load on upstream homeservers by @S7evinK in https://github.com/matrix-org/sliding-sync/pull/290Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.9...v0.99.10
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Redact events in the DB on m.room.redaction.
m.room.redaction. (https://github.com/matrix-org/sliding-sync/pull/280)debug.ReadBuildInfo. (https://github.com/matrix-org/sliding-sync/pull/285)Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.8...v0.99.9
Nothing published for this version
Nothing published for this version
Nothing published for this version
Docker images available at: https://github.com/matrix-org/sliding-sync/pkgs/container/sliding-sync
Docker images available at: https://github.com/matrix-org/sliding-sync/pkgs/container/sliding-sync
Bug fixes:
Nothing published for this version
Nothing published for this version
Nothing published for this version
The SYNCV3_JAEGER_URL env var has been replaced with SYNCV3_OTLP_URL, which is an HTTPS URL to a suitable OTLP collector, typically listening on :4318
The SYNCV3_JAEGER_URL env var has been replaced with SYNCV3_OTLP_URL, which is an HTTPS URL to a suitable OTLP collector, typically listening on :4318. The proxy can optionally send HTTP Basic authentication to this endpoint via the env vars SYNCV3_OTLP_USERNAME and SYNCV3_OTLP_PASSWORD.
Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.6...v0.99.7
Nothing published for this version
Don't tell clients about messages from ignored users that the proxy has learned about from other users' pollers.
M_UNKNOWN_TOKEN for unknown tokens (https://github.com/matrix-org/sliding-sync/pull/253)timestamp to room responses. (https://github.com/matrix-org/sliding-sync/pull/247)m.server example from readme by @turt2live in https://github.com/matrix-org/sliding-sync/pull/257Full Changelog: https://github.com/matrix-org/sliding-sync/compare/v0.99.5...v0.99.6
Nothing published for this version
Nothing published for this version
One column per quarter.