This commit is contained in:
anoadragon453
2025-10-10 11:12:49 +00:00
parent ff35750c61
commit 3eb80c4deb
4 changed files with 16 additions and 2 deletions

View File

@@ -1899,6 +1899,13 @@ database migrations are complete. You should wait until background updates from
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-v11400"><a class="header" href="#upgrading-to-v11400">Upgrading to v1.140.0</a></h1>
<h2 id="users-of-synapse-s3-storage-provider-must-update-the-module-to-v160"><a class="header" href="#users-of-synapse-s3-storage-provider-must-update-the-module-to-v160">Users of <code>synapse-s3-storage-provider</code> must update the module to <code>v1.6.0</code></a></h2>
<p>Deployments that make use of the
<a href="https://github.com/matrix-org/synapse-s3-storage-provider/">synapse-s3-storage-provider</a>
module must update it to
<a href="https://github.com/matrix-org/synapse-s3-storage-provider/releases/tag/v1.6.0">v1.6.0</a>,
otherwise users will be unable to upload or download media.</p>
<h1 id="upgrading-to-v11390"><a class="header" href="#upgrading-to-v11390">Upgrading to v1.139.0</a></h1>
<h2 id="register-requests-from-old-application-service-implementations-may-break-when-using-mas"><a class="header" href="#register-requests-from-old-application-service-implementations-may-break-when-using-mas"><code>/register</code> requests from old application service implementations may break when using MAS</a></h2>
<p>Application Services that do not set <code>inhibit_login=true</code> when calling <code>POST /_matrix/client/v3/register</code> will receive the error

File diff suppressed because one or more lines are too long

File diff suppressed because one or more lines are too long

View File

@@ -285,6 +285,13 @@ database migrations are complete. You should wait until background updates from
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-v11400"><a class="header" href="#upgrading-to-v11400">Upgrading to v1.140.0</a></h1>
<h2 id="users-of-synapse-s3-storage-provider-must-update-the-module-to-v160"><a class="header" href="#users-of-synapse-s3-storage-provider-must-update-the-module-to-v160">Users of <code>synapse-s3-storage-provider</code> must update the module to <code>v1.6.0</code></a></h2>
<p>Deployments that make use of the
<a href="https://github.com/matrix-org/synapse-s3-storage-provider/">synapse-s3-storage-provider</a>
module must update it to
<a href="https://github.com/matrix-org/synapse-s3-storage-provider/releases/tag/v1.6.0">v1.6.0</a>,
otherwise users will be unable to upload or download media.</p>
<h1 id="upgrading-to-v11390"><a class="header" href="#upgrading-to-v11390">Upgrading to v1.139.0</a></h1>
<h2 id="register-requests-from-old-application-service-implementations-may-break-when-using-mas"><a class="header" href="#register-requests-from-old-application-service-implementations-may-break-when-using-mas"><code>/register</code> requests from old application service implementations may break when using MAS</a></h2>
<p>Application Services that do not set <code>inhibit_login=true</code> when calling <code>POST /_matrix/client/v3/register</code> will receive the error