docs: document expand/contract pattern for dropping DB columns - #787
Closed
gaidheal1 wants to merge 9 commits into
Closed
docs: document expand/contract pattern for dropping DB columns#787gaidheal1 wants to merge 9 commits into
gaidheal1 wants to merge 9 commits into
Conversation
development → staging
development → staging
development → staging
The hour/minute duration inputs shared a .row class with the completed-date/time row. The small-screen media query flipped all .row elements to flex-direction: column, stacking the duration fields instead of keeping them side by side. Scope the column layout to the date/time row only. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Publishing an Announcement now pushes a WebSocket "announcement_published" event to online players, which invalidates the announcements/unread-count queries so the Navbar badge appears immediately instead of only on refresh or remount. - Announcement.save() broadcasts on the unpublished->published transition - publish_selected_announcements admin action saves rows individually (not queryset.update()) so the broadcast actually fires - frontend wires the new action into handleGlobalWebSocketEvent / WebSocketContext to invalidate the relevant react-query keys Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
…realtime-badge feat: broadcast announcement badge updates in real time
Deploy: staging → main
Root-cause the 2026-08-14 production UndefinedColumn errors on Character.can_link: web, celery, and celery-beat deploy independently on Render, and only web runs migrate via preDeployCommand. The migration dropping can_link landed in the same deploy as the code change that stopped using it, so celery/celery-beat kept erroring on the old column reference until their own deploys caught up. The current can_link code (derived property, is_reserved field) is already correct - this documents the two-deploy process needed to avoid the same stale-worker window on future column removals.
2 tasks
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.
Superseded — branch renamed to
task/fix-sentry-issuesand continued in #788 (I don't have permission to delete the oldclaude/prod-redis-query-errors-c0dzdgbranch, so closing this PR instead).