This commit is contained in:
anoadragon453
2025-11-27 16:46:20 +00:00
parent bd27e04f3c
commit 3158e48a21
5 changed files with 20 additions and 6 deletions

View File

@@ -1938,6 +1938,10 @@ each upgrade are complete before moving on to the next upgrade, to avoid
stacking them up. You can monitor the currently running background updates with
<a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p>
<h1 id="upgrading-to-v11440"><a class="header" href="#upgrading-to-v11440">Upgrading to v1.144.0</a></h1>
<h2 id="worker-support-for-unstable-msc4140-restart-endpoint"><a class="header" href="#worker-support-for-unstable-msc4140-restart-endpoint">Worker support for unstable MSC4140 <code>/restart</code> endpoint</a></h2>
<p>The following unstable endpoint pattern may now be routed to worker processes:</p>
<pre><code>^/_matrix/client/unstable/org.matrix.msc4140/delayed_events/.*/restart$
</code></pre>
<h2 id="unstable-mutual-rooms-endpoint-is-now-behind-an-experimental-feature-flag"><a class="header" href="#unstable-mutual-rooms-endpoint-is-now-behind-an-experimental-feature-flag">Unstable mutual rooms endpoint is now behind an experimental feature flag</a></h2>
<p>The unstable mutual rooms endpoint from
<a href="https://github.com/matrix-org/matrix-spec-proposals/pull/2666">MSC2666</a>
@@ -12163,10 +12167,13 @@ information.</p>
# User directory search requests
^/_matrix/client/(r0|v3|unstable)/user_directory/search$
# Unstable MSC4140 support
^/_matrix/client/unstable/org.matrix.msc4140/delayed_events(/.*/restart)?$
</code></pre>
<p>Additionally, the following REST endpoints can be handled for GET requests:</p>
<pre><code>^/_matrix/client/(api/v1|r0|v3|unstable)/pushrules/
^/_matrix/client/unstable/org.matrix.msc4140/delayed_events
<pre><code># Push rules requests
^/_matrix/client/(api/v1|r0|v3|unstable)/pushrules/
# Account data requests
^/_matrix/client/(r0|v3|unstable)/.*/tags

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View File

@@ -286,6 +286,10 @@ each upgrade are complete before moving on to the next upgrade, to avoid
stacking them up. You can monitor the currently running background updates with
<a href="usage/administration/admin_api/background_updates.html#status">the Admin API</a>.</p>
<h1 id="upgrading-to-v11440"><a class="header" href="#upgrading-to-v11440">Upgrading to v1.144.0</a></h1>
<h2 id="worker-support-for-unstable-msc4140-restart-endpoint"><a class="header" href="#worker-support-for-unstable-msc4140-restart-endpoint">Worker support for unstable MSC4140 <code>/restart</code> endpoint</a></h2>
<p>The following unstable endpoint pattern may now be routed to worker processes:</p>
<pre><code>^/_matrix/client/unstable/org.matrix.msc4140/delayed_events/.*/restart$
</code></pre>
<h2 id="unstable-mutual-rooms-endpoint-is-now-behind-an-experimental-feature-flag"><a class="header" href="#unstable-mutual-rooms-endpoint-is-now-behind-an-experimental-feature-flag">Unstable mutual rooms endpoint is now behind an experimental feature flag</a></h2>
<p>The unstable mutual rooms endpoint from
<a href="https://github.com/matrix-org/matrix-spec-proposals/pull/2666">MSC2666</a>

View File

@@ -415,10 +415,13 @@ information.</p>
# User directory search requests
^/_matrix/client/(r0|v3|unstable)/user_directory/search$
# Unstable MSC4140 support
^/_matrix/client/unstable/org.matrix.msc4140/delayed_events(/.*/restart)?$
</code></pre>
<p>Additionally, the following REST endpoints can be handled for GET requests:</p>
<pre><code>^/_matrix/client/(api/v1|r0|v3|unstable)/pushrules/
^/_matrix/client/unstable/org.matrix.msc4140/delayed_events
<pre><code># Push rules requests
^/_matrix/client/(api/v1|r0|v3|unstable)/pushrules/
# Account data requests
^/_matrix/client/(r0|v3|unstable)/.*/tags