For backwards compatibility it is also sent as the access_token Usage of the legacy routes should be considered deprecated.Īdditionally, Synapse has supported sending the application service access token Synapse now attempts the versioned appservice paths before falling back to the
Upgrading to v1.81.0 Application service path & authentication deprecations In general, you will need to undo any changes made during the upgradeĭebian: # replace `1.3.0` and `stretch` accordingly:ĭpkg -i matrix-synapse-p圓_1.3.0+stretch1_b Rollback process, this will be noted below. Rolling back to previous releases can be difficult, due to database Server version with: # you may need to replace 'localhost:8008' if synapse is not configured To check whether your update was successful, you can check the running It's probably easiest to run poetry install -extras all.
poetry install -extras postgres -extras oidc. Include any relevant extras with -extras, e.g.
If you're using poetry to manage a Synapse installation, run: poetry install Include any relevant extras between square brackets, e.g. For example, if Synapse is installed in a virtualenv in ~/synapse/env then If you're running Synapse in a virtualenv, make sure to activate it before Obtain the latest version of the source code. If Synapse was installed from source, then: Version by running: pip install -upgrade matrix-synapse If Synapse was installed using pip then upgrade to the latest You will need to follow the normal process for upgrading those packages. If Synapse was installed using prebuilt packages, PostgreSQL, and removes support for versions Synapse follows upstream lifecycles for Python and The extra instructions that may be required are listed later inĬheck that your versions of Python and PostgreSQL are still The version you currently have installed to the current version of
0 kommentar(er)
