fix: broadcast WebSocket invalidation on all Message creation paths - #182
Merged
Conversation
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Owner
Author
|
🎉 This PR is included in version 1.6.1-alpha.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This was referenced May 28, 2026
Owner
Author
|
🎉 This PR is included in version 1.6.1 🎉 The release is available on GitHub release 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.
Summary
post_savesignal on theMessagemodel inadministration/signals.pybroadcast_invalidate(["messages"])with the correct group (user_<pk>for user-scoped messages,globalfor broadcast messages)AdministrationConfig.ready()so it loads on app startuptransactions/tasks.py'screate_message()helper — messages created via Django shell, admin, or any other path did not push updates to the frontendTest plan
Messagevia Django admin or shell — it should appear in the inbox immediately without a page refreshMessage— only that user's inbox should updateMessage(user=None) — all connected clients should receive the invalidation🤖 Generated with Claude Code