This commit is contained in:
erikjohnston
2025-02-24 12:07:50 +00:00
parent 3d34edc667
commit 87cacc8151
5 changed files with 32 additions and 6 deletions
+11
View File
@@ -285,6 +285,17 @@ 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-v11260"><a class="header" href="#upgrading-to-v11260">Upgrading to v1.126.0</a></h1>
<h2 id="room-list-publication-rules-change"><a class="header" href="#room-list-publication-rules-change">Room list publication rules change</a></h2>
<p>The default <a href="usage/configuration/config_documentation.html#room_list_publication_rules"><code>room_list_publication_rules</code></a> setting was changed to disallow
anyone (except server admins) from publishing to the room list by default.</p>
<p>This is in line with Synapse policy of locking down features by default that can
be abused without moderation.</p>
<p>To keep the previous behavior of allowing publication by default, add the
following to the config:</p>
<pre><code class="language-yaml">room_list_publication_rules:
- &quot;action&quot;: &quot;allow&quot;
</code></pre>
<h1 id="upgrading-to-v11220"><a class="header" href="#upgrading-to-v11220">Upgrading to v1.122.0</a></h1>
<h2 id="dropping-support-for-postgresql-11-and-12"><a class="header" href="#dropping-support-for-postgresql-11-and-12">Dropping support for PostgreSQL 11 and 12</a></h2>
<p>In line with our <a href="deprecation_policy.html">deprecation policy</a>, we've dropped