Closed
Description
Here is the v1.13 changelog to follow our progress.
To be sure we don't miss anything, ALL entries of the changelog (except the section about internal changes) should appear here in the same order and category. The ones that we have to implement should be linked to an issue and/or a PR or commit in this repository. If an extra step is necessary when the version is released (like moving it from an unstable feature flag), a subtask should be created. The ones that don't impact us should be struck. The "contributed by"s should be removed to avoid pinging users.
Ruma-specific tasks (when the version is released)
- Allow links to new version of the spec in
xtask::ci::spec_links
Add initial support for Matrix 1.13 #1980 - Add a new variant to
ruma_common::api::MatrixVersion
Add initial support for Matrix 1.13 #1980 - Change spec links that don't point to
latest
to point to the new version, where it makes sense Add initial support for Matrix 1.13 #1980
1.1 Client-Server API
New Endpoints
- Add
POST /_matrix/client/v3/rooms/{roomId}/report
as per MSC4151. (#1938, #2028) client-api: Addreport_room
endpoint #1967- Move out of
unstable-msc4151
- Move out of
Backwards Compatible Changes
- Add error codes to
requestToken
endpoints (MSC4178). (#1944) client-api: Add new error codes #1976 - Remove reply fallbacks, as per MSC2781. (#1994) events: Do not generate reply fallbacks anymore 🎉 #1964
-
Clarify the allowed HTTP methods in CORS responses, as per MSC4138. (#1995, #2011) - Add new
M_USER_SUSPENDED
error code behaviour, as per MSC3823. (#2014) client-api: Add new error codes #1976
Spec Clarifications
- The
reason
parameter inPOST /_matrix/client/v3/rooms/{roomId}/report/{eventId}
can be omitted instead of left blank as per MSC2414. (#1938) Batch of small docs changes #1963 - Correct OpenAPI specification for query parameters to
GET /_matrix/client/v3/thirdparty/location/{protocol}
endpoint. (#1947) Batch of small docs changes #1963 -
Sort VoIP events semantically. (#1967) - Clarify that servers must forward custom keys in
PusherData
when sending notifications to the push gateway. (#1973) push: Allow to add custom data for pushers #1965 -
Clarify formats of string types. (#1978, #1979, #1980) -
Clarify that the async upload endpoint will return 404 in some cases. (#1983) -
Remove distinction betweenStateFilter
andRoomEventFilter
. (#2015) -
Add hyperlinks throughout the specification. (#2016) -
Usejson
instead ofjson5
for syntax highlighting. (#2017) -
Specify order that one-time keys are issued by/keys/claim
, as per MSC4225. (#2029)
1.2 Server-Server API
Backwards Compatible Changes
Spec Clarifications
-
Add 403 error response to/_matrix/federation/v1/state_ids/{roomId}
. (#1926)
1.3 Application Service API
Backwards Compatible Changes
- Allow sending ephemeral data to application services, as per MSC2409. (#2018) appservice-api: Stabilize support for sending ephemeral data to appservices #1977
1.4 Identity Service API
No significant changes.
1.5 Push Gateway API
Spec Clarifications
- Document the schema of
PusherData
. (#1968) push: Allow to add custom data for pushers #1965 -
The path of HTTP pusher URLs is fixed to/_matrix/push/v1/notify
. (#1974)
1.6 Room Versions
Spec Clarifications
-
Clarify rule 4.3.1 of the auth rules in room version 11 to state which event’ssender
thestate_key
needs to match. (#2024)
1.7 Appendices
Spec Clarifications
-
Remove note about reference implementations. (#1966)