matrix-synapse (0.99.0-1) unstable; urgency=medium

  This version of the package introduces support for the Server-to-Server
  Spec r0.1. Since this version of the specification, self-signed
  certificates will no longer be valid for homeservers. While 0.99.0 still
  accepts self-signed certificates, the next release of Synapse will not.

  It is critical that you configure a valid TLS certificate. Synapse will
  not automatically invalidate or warn about existing self-signed
  certificates.

  Starting from 0.99.0, Synapse supports ACME protocol to request
  certificates from Let’s Encrypt, but this code is not yet available
  in Debian packages, which means that you need to set it up manually
  for now.

  Please note that if your homeserver runs under a different domain
  name than your server name, you will need to configure the .well-known
  resource; just having an SRV record will not be enough to federate
  with Synapse 1.0 servers.

  See /usr/share/doc/matrix-synapse/misc/MSC1711_certificates_FAQ.md.gz
  for more details.

 -- Andrej Shadura <andrewsh@debian.org>  Sat, 09 Feb 2019 15:21:23 +0100

matrix-synapse (0.34.0-1) unstable; urgency=medium

  From 0.34.0~rc2 on, matrix-synapse runs using Python 3. This contrasts
  with packages the upstream provides, where matrix-synapse is a Python 2
  version, and the Python 3 version is shipped as matrix-synapse-py3.

 -- Andrej Shadura <andrewsh@debian.org>  Fri, 21 Dec 2018 13:34:26 +0100