Skip to content

fix: send the read request regardless of read receipt privacy settings - #1853

Merged
MartinCupela merged 1 commit into
masterfrom
fix/read-receipts-not-guard-mark-read-calls
Sep 7, 2026
Merged

fix: send the read request regardless of read receipt privacy settings#1853
MartinCupela merged 1 commit into
masterfrom
fix/read-receipts-not-guard-mark-read-calls

Conversation

@MartinCupela

Copy link
Copy Markdown
Contributor

Goal

  1. Do not guard marking channel or thread read by read-receipts setting (privacy_settings.read_receipts.enabled). It is unrelated to the ability to mark a channel / thread.
  2. The PR also adds user permission check to mark channel read or unread to already existing channel config check.

@MartinCupela
MartinCupela merged commit 59d8f31 into master Sep 7, 2026
7 checks passed
@MartinCupela
MartinCupela deleted the fix/read-receipts-not-guard-mark-read-calls branch September 7, 2026 09:10
github-actions Bot pushed a commit that referenced this pull request Sep 7, 2026
## [9.52.1](v9.52.0...v9.52.1) (2026-09-07)

### Bug Fixes

* isolate event listener errors from the dispatch loop ([#1850](#1850)) ([dc56e57](dc56e57))
* send the read request regardless of read receipt privacy settings ([#1853](#1853)) ([59d8f31](59d8f31))
@stream-ci-bot

Copy link
Copy Markdown

🎉 This PR is included in version 9.52.1 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants