docs: track react v14 notifications and composer follow-up#3114
Merged
docs: track react v14 notifications and composer follow-up#3114
Conversation
MartinCupela
approved these changes
Apr 14, 2026
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
2 participants
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.
🎯 Goal
Track the latest post-
dc16bb584React v14 docs follow-up work so the public v14 docs and migration guide stay aligned with the current SDK surface.🛠 Implementation details
ai-docs/breaking-changes.mdandai-docs/docs-plan.mdto78934929a2b1b6d82f09736aada08c57c194d45eonlySenderCanEditremoval and the legacy notification callback /ConnectionStatusremovalmessage-composerdocs tree and remove stale dead-path references🎨 UI Changes
None.