dandri/synapse
1
0
Fork 0
mirror of https://github.com/element-hq/synapse.git synced 2026-08-28 22:18:18 +00:00
Code Issues Packages Projects Releases Wiki Activity

deploy: facb81d97b

Browse Source
This commit is contained in:
anoadragon453
2025-10-29 11:58:30 +00:00
parent 09e57f6d66
commit 28c3bf6856
6 changed files with 18 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files
latest/print.html
+7 -2
View File
@@ -1881,7 +1881,7 @@ v1.61.0.</p>
<tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr>
<tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr>
<tr><td>v1.98.0 – v1.105.0</td><td>v1.96.0</td></tr>
<tr><td>v1.105.1 – v1.140.0</td><td>v1.100.0</td></tr>
<tr><td>v1.105.1 – v1.141.0</td><td>v1.100.0</td></tr>
</tbody></table>
<h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2>
<p>You need to read all of the upgrade notes for each version between your current
@@ -1899,6 +1899,11 @@ 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-v11410"><a class="header" href="#upgrading-to-v11410">Upgrading to v1.141.0</a></h1>
<h2 id="docker-images-now-based-on-debian-trixie-with-python-313"><a class="header" href="#docker-images-now-based-on-debian-trixie-with-python-313">Docker images now based on Debian <code>trixie</code> with Python 3.13</a></h2>
<p>The Docker images are now based on Debian <code>trixie</code> and use Python 3.13. If you
are using the Docker images as a base image you may need to e.g. adjust the
paths you mount any additional Python packages at.</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
@@ -7208,7 +7213,7 @@ These limits are applied in addition to the <code>max_upload_size</code> limit a
<p><code>localdb_enabled</code> (boolean): Set to false to disable authentication against the local password database. This is ignored if <code>enabled</code> is false, and is only useful if you have other <code>password_providers</code>. Defaults to <code>true</code>.</p>
</li>
<li>
<p><code>pepper</code> (string|null): Set the value here to a secret random string for extra security. DO NOT CHANGE THIS AFTER INITIAL SETUP! Defaults to <code>null</code>.</p>
<p><code>pepper</code> (string|null): A secret random string that will be appended to user's passwords before they are hashed. This improves the security of short passwords. DO NOT CHANGE THIS AFTER INITIAL SETUP! Defaults to <code>null</code>.</p>
</li>
<li>
<p><code>policy</code> (object): Define and enforce a password policy, such as minimum lengths for passwords, etc. This is an implementation of MSC2000.</p>
latest/schema/synapse-config.schema.json
+2 -2
View File
@@ -1,6 +1,6 @@
{
"$schema": "https://element-hq.github.io/synapse/latest/schema/v1/meta.schema.json",
"$id": "https://element-hq.github.io/synapse/schema/synapse/v1.140/synapse-config.schema.json",
"$id": "https://element-hq.github.io/synapse/schema/synapse/v1.141/synapse-config.schema.json",
"type": "object",
"properties": {
"modules": {
@@ -3893,7 +3893,7 @@
"string",
"null"
],
"description": "Set the value here to a secret random string for extra security. DO NOT CHANGE THIS AFTER INITIAL SETUP!",
"description": "A secret random string that will be appended to user's passwords before they are hashed. This improves the security of short passwords. DO NOT CHANGE THIS AFTER INITIAL SETUP!",
"default": null
},
"policy": {
latest/searchindex.js
+1 -1
View File
File diff suppressed because one or more lines are too long
latest/searchindex.json
+1 -1
View File
File diff suppressed because one or more lines are too long
latest/upgrade.html
+6 -1
View File
@@ -267,7 +267,7 @@ v1.61.0.</p>
<tr><td>v1.85.0 – v1.91.2</td><td>v1.83.0</td></tr>
<tr><td>v1.92.0 – v1.97.0</td><td>v1.90.0</td></tr>
<tr><td>v1.98.0 – v1.105.0</td><td>v1.96.0</td></tr>
<tr><td>v1.105.1 – v1.140.0</td><td>v1.100.0</td></tr>
<tr><td>v1.105.1 – v1.141.0</td><td>v1.100.0</td></tr>
</tbody></table>
<h2 id="upgrading-from-a-very-old-version"><a class="header" href="#upgrading-from-a-very-old-version">Upgrading from a very old version</a></h2>
<p>You need to read all of the upgrade notes for each version between your current
@@ -285,6 +285,11 @@ 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-v11410"><a class="header" href="#upgrading-to-v11410">Upgrading to v1.141.0</a></h1>
<h2 id="docker-images-now-based-on-debian-trixie-with-python-313"><a class="header" href="#docker-images-now-based-on-debian-trixie-with-python-313">Docker images now based on Debian <code>trixie</code> with Python 3.13</a></h2>
<p>The Docker images are now based on Debian <code>trixie</code> and use Python 3.13. If you
are using the Docker images as a base image you may need to e.g. adjust the
paths you mount any additional Python packages at.</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
latest/usage/configuration/config_documentation.html
+1 -1
View File
@@ -3395,7 +3395,7 @@ These limits are applied in addition to the <code>max_upload_size</code> limit a
<p><code>localdb_enabled</code> (boolean): Set to false to disable authentication against the local password database. This is ignored if <code>enabled</code> is false, and is only useful if you have other <code>password_providers</code>. Defaults to <code>true</code>.</p>
</li>
<li>
<p><code>pepper</code> (string|null): Set the value here to a secret random string for extra security. DO NOT CHANGE THIS AFTER INITIAL SETUP! Defaults to <code>null</code>.</p>
<p><code>pepper</code> (string|null): A secret random string that will be appended to user's passwords before they are hashed. This improves the security of short passwords. DO NOT CHANGE THIS AFTER INITIAL SETUP! Defaults to <code>null</code>.</p>
</li>
<li>
<p><code>policy</code> (object): Define and enforce a password policy, such as minimum lengths for passwords, etc. This is an implementation of MSC2000.</p>