Repository navigation
docs(v10-breaking-changes): moderation v2 flag, flat partial-update set, Date guards - #2006
Merged
Merged
Conversation
…et, Date guards - client.moderation mute / unmute / flag need the moderation v2 feature flag (403 otherwise) - every partial update keeps custom fields flat in set; custom is a reserved key there - ts instanceof Date is a silent timestamp failure - matching rows in the still-compiles table
oliverlaz
requested review from
MartinCupela,
NikolaGoranNaumovski,
isekovanic and
szuperaz
as code owners
November 6, 2026 12:42
|
🎉 This PR is included in version 10.0.0-rc.35 🎉 The release is available on: Your semantic-release bot 📦🚀 |
|
🎉 This PR is included in version 10.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
CLA
Description of the changes, What, Why and How?
Ticket: REACT-1307.
A v14/v9 → v15/v10 migration run surfaced three things
v10-breaking-changes.mddidn't say. Docs only.client.muteUser/unmuteUser/flagUser/flagMessagehit the v1/moderation/*endpoints. They were removed in feat!: remove hand-written types and API wrappers #1836, and theclient.moderationreplacements only call/api/v2/moderation/{mute,unmute,flag}. On an app without the v2 moderation feature flag these fail with403"this endpoint needs a feature flag, contact support to get it enabled" (reported on10.0.0-rc.34). The moderation entry now says so and suggests trying a mute and a flag against the app before upgrading.updateUsersPartial. It now lists every partial update (updateMessagePartial,channel.updatePartial,channel.updateMemberPartial,updateThreadPartial), sayscustomis a reserved key inset(rejected withfield `custom` is reserved), and notes TypeScript can't catch it because every generatedsetisRecord<string, any>.ts instanceof Datejoins the silent timestamp failures.The "Behaviour changes that still compile" table gets matching rows.
React guide counterpart: GetStream/stream-chat-react#3416.
Changelog
setin partial updates,Dateguards on timestamps