The Wire · Showcase
STUDIO SELF-IMPORT BUG FIXED, REALTIME SHIPS FANOUT METRICS
By RepoJournal · Filed · About Supabase
Supabase shipped a critical fix for TanStack Studio's local dev environment while Realtime v2.120.0 lands broadcast telemetry and cluster scaling improvements.
The UI patterns module was re-exporting itself on case-insensitive filesystems [1], breaking every local build of Studio across macOS and Windows. The fix adds a CI guard to catch this class of bug before it ships again. Meanwhile, Realtime v2.120.0 [2] introduces fanout broadcast metrics to track "how often we have hits when broadcasting" [3], plus a two-phase view adoption feature for cluster growth that should smooth horizontal scaling. On the Dashboard side, a new Top Blocker overview card surfaces queries that are blocking more than 3 others [4], reducing signal noise by only showing danger state when blocks exceed 10 seconds [5]. The management API spec circular reference that was breaking the weekly docs workflow [6] is now resolved. Across all three desks, 6 commits landed with 1 production release this period.
One email a day. Unsubscribe in one click.
Keep up with Supabase in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Pull latest supabase/supabase if you run Studio locally on macOS or Windows supabase/supabase [immediate]
- → Upgrade to Realtime v2.120.0 in your next deployment window supabase/realtime [plan]
- → Monitor the new Top Blocker card in your database connections dashboard supabase/supabase [monitor]
References
- [1] fix(ui-patterns): fix admonition self-import + add case-sensitivity guard ↗ supabase/supabase
- [2] v2.120.0 ↗ supabase/realtime
- [3] feat: collect fanout broadcast metric ↗ supabase/realtime
- [4] Add top blocker overview card ↗ supabase/supabase
- [5] Blocked by card to only highlight if any query is blocked longer than 10 sec ↗ supabase/supabase
- [6] fix: resolve mgmt api specs $refs manually to handle circular error (#48281) supabase/supabase