-
Notifications
You must be signed in to change notification settings - Fork 10.7k
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
fix: Handle encrypted pinned messages #32380
Conversation
Looks like this PR is ready to merge! 🎉 |
🦋 Changeset detectedLatest commit: f72ff36 The changes in this PR will be included in the next version bump. This PR includes changesets to release 32 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 @@
## develop #32380 +/- ##
===========================================
- Coverage 56.63% 56.56% -0.07%
===========================================
Files 2495 2491 -4
Lines 55242 55041 -201
Branches 11435 11391 -44
===========================================
- Hits 31284 31136 -148
+ Misses 21261 21246 -15
+ Partials 2697 2659 -38
Flags with carried forward coverage won't be shown. Click here to find out more. |
aa83f69
to
f72ff36
Compare
Proposed changes (including videos or screenshots)
Decrypt encrypted pinned messages in E2EE channels.
Introducing a new message type -
message_pinned_e2e
for encrypted pinned messages. The messages with this type will be decrypted before being shown.Issue(s)
Steps to test or reproduce
Further comments
E2EE-14