-
-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
matrix-synapse: 1.3.1 -> 1.4.0 #70469
Conversation
@GrahamcOfBorg test matrix-synapse |
e39954f
to
5778c45
Compare
5778c45
to
4502bc8
Compare
Ok pacien I'll create |
Already broken on darwin, no change here unfortunately :( (macos 10.13, happy on non-nixos linux x86_64 though) |
Any movement on this? Setting up a matrix server soon but I'm waiting for 1.4 to be merged first. |
I'll finished this tonight or tomorrow morning |
The deprecation breaks eval. I'll have a bit of time this afternoon to fix it :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So, just did a review and addressed some minor issues. I deployed the current state onto my personal homeserver to check if I encounter any regressions. @pacien @Vskilet please review.
Regarding my changes:
- it seems as
account_threepid_delegates
is simply a block which takes an email and amsisdn
value (or am I missing something here?) - Dropped the deprecated
trusted_third_party_id_servers
. People will now get a meaningful error message when using this and upgrading to matrix-synapse 1.4.0.
It would be awesome if the merger of this PR would squash all commits into a single commit with a Co-Authored-by
statement for @pacien and me.
@NixOS/backports @Ekleog @pacien I'd propose to backport this even though it contains breaking changes: the old behavior for email activation (which used to rely on trusted_third_party_id_servers
) will be disabled on hosted identity-servers (matrix.org, vector.im) in December 2019 (https://matrix.org/blog/2019/10/03/synapse-1-4-0-released), so the old behavior can't be supported after that.
Also, people should notice the change as mkRemovedOptionModule
already raises an evaluation error, right?
Correct @Ma27, if they make a decision like this we unfortunately won't have any choice in the matter. |
@Ma27 I didn't have the time to review this yet, so this is neither a r+ or r- and I'll let you handle review, but agree that your arguments appear to me as requiring a backport. Thank you for handling this! :) |
@ofborg test matrix-synapse |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Bumps `matrix-synapse` to version 1.4.0[1]. With this version the following changes in the matrix-synapse module were needed: * Removed `trusted_third_party_id_servers`: option is marked as deprecated and ignored by matrix-synapse[2]. * Added `account_threepid_delegates` options as replacement for 3rdparty server features[3]. * Added `redaction_retention_period` option to configure how long redacted options should be kept in the database. * Added `ma27` as maintainer for `matrix-synapse`. Co-Authored-By: Notkea <[email protected]> Co-authored-by: Maximilian Bosch <[email protected]> [1] https://matrix.org/blog/2019/10/03/synapse-1-4-0-released [2] matrix-org/synapse#5875 [3] matrix-org/synapse#5876
5f84e12
to
3724223
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just squashed the commits into a single one as all changes are actually related (all module changes are needed due to the matrix-synapse bump), so bisecting gets noticeable easier that way. Also added @pacien and myself as co-authors.
I'm running those changes with matrix-synapse 1.4.0 on my personal Matrix setup since Friday without encountering any issues. Also tested/reviewed this with @calbrecht this evening.
I'd wait for ofborg to build and merge/backport (to 19.09) then. IMHO it's fine to not backport to 19.03 as those changes are actually a breaking change and 19.03 support will be dropped before the legacy features are disabled on Matrix.org infrastructure.
@GrahamcOfBorg test matrix-synapse
Motivation for this change
Latest release
https://github.com/matrix-org/synapse/releases/tag/v1.4.0
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)Notify maintainers
cc @Ma27 @pacien