-
Notifications
You must be signed in to change notification settings - Fork 10.5k
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
chore!: Update default E2EE settings behavior #33361
Conversation
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: a0d56f4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## release-7.0.0 #33361 +/- ##
=================================================
- Coverage 74.80% 74.79% -0.02%
=================================================
Files 468 467 -1
Lines 20678 20641 -37
Branches 5275 5262 -13
=================================================
- Hits 15469 15439 -30
+ Misses 4594 4590 -4
+ Partials 615 612 -3
Flags with carried forward coverage won't be shown. Click here to find out more. |
cb512e1
to
335ae33
Compare
50abbe6
to
bf02ce5
Compare
d1aa5f9
to
374979f
Compare
09c1b34
to
3099c34
Compare
8f174b6
to
ebe7a29
Compare
ec22306
to
d9a36fa
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.
Did we change the setting creation code in another PR? The this.add(...
cause otherwise the code for new workspaces will retain the current behavior as migrations won't run on clean envs
Ohhh, nice catch!! I had done that, but it got lost when solving conflicts. |
Proposed changes (including videos or screenshots)
We introduced a new E2EE settings with 6.x release -
E2E_Allow_Unencrypted_Messages
. Earlier their default value was kept in a way to not change the default behavior.We decided to change this default behavior in the major 7.0.0 release and now by default users shouldn't be allowed to send un-encrypted messages in encrypted rooms.
Issue(s)
Steps to test or reproduce
Further comments
E2EE2-69