124 wires and counting

$ follow Supabase

Keep up with Supabase in about 3 minutes: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

fair warning: these emails are deeply technical. diffs, version numbers, CVEs, benchmark deltas. if that's not your idea of a good read, this isn't your newsletter.

Folds into your digest — weekly by default, monthly if you prefer. Unsubscribe in one click.

$ status

wire 2026-08-03
stories 18

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

STUDIO SHIPPING SAFETY RAILS AS REALTIME HITS 2.122.0

By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology

Supabase Studio locked down form state protection across replication and OAuth flows while the Realtime service adds group lookup to its admin dashboard.

Studio is systematically hardening user interactions against data loss. The team shipped confirm-before-discard for replication destination forms [2], so closing the Add/Edit sheet now prompts rather than silently dumps in-progress state. That follows a similar safety pattern applied to OAuth impersonation warnings [3], which now alerts users when a requester presents a trusted partner name but redirects to an unrelated host. Studio also fixed sheets stealing focus from the page tab order [5], resolving a navigation regression that broke expected keyboard flow. Separately, action failures in API authorization and AWS Marketplace flows now display inline and persistent rather than disappearing into transient toasts [4]. On the Realtime side, v2.122.0 [6] shipped with group lookup support in the admin muster dashboard [7], expanding visibility into connection groups for operational teams. The docs desk migrated resources and getting-started guides to use shared ContentListings components [1], which restores PostHog telemetry tracking and contribution paths that hand-rolled implementations were missing.

Action items

References

  1. [1] feat(docs): migrate resources and getting-started to ContentListings ↗ supabase/supabase
  2. [2] fix(studio): confirm before discarding dirty replication destination forms ↗ supabase/supabase
  3. [3] feat(studio): oauth impersonation warning on authorize ↗ supabase/supabase
  4. [4] show API and AWS authorization errors inline ↗ supabase/supabase
  5. [5] fix sheets stealing focus (#48521) supabase/supabase ↗
  6. [6] v2.122.0 ↗ supabase/realtime
  7. [7] feat: add group lookup to admin muster dashboard ↗ supabase/realtime

Quick answers

What shipped in Supabase on August 3, 2026?
Supabase Studio locked down form state protection across replication and OAuth flows while the Realtime service adds group lookup to its admin dashboard. In total, 9 commits, 8 pull requests, and 1 releases landed.
Who contributed to Supabase on August 3, 2026?
4 developers shipped this update, including dnywh, realtime-release-bot[bot], edgurgel, and semantic-release-bot.
What were the notable Supabase updates?
feat(docs): migrate resources and getting-started to ContentListings, fix(studio): confirm before discarding dirty replication destination forms, and feat(studio): oauth impersonation warning on authorize.