151 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-17
stories 24

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

SUPABASE STUDIO TIGHTENS PRIVATELINK UX ACROSS FOUR COMMITS

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

Four linked PRs ship clarity to PrivateLink configuration and MFA backup flows, replacing ambiguous copy with resource IDs and clearer field ordering.

Studio's PrivateLink interface now displays AWS account IDs and connection details that properly distinguish between primary and read replica configurations [1]. The labeling shift from "AWS account" to "connection" closes a gap where operators couldn't tell which resource ID belonged where. Paired with that, MFA backup authenticator copy got rewritten to clarify you're adding a second authenticator app, not another account identity [2], and the control moved up next to the warning instead of sitting at the card's bottom. Status labels extracted into a single lookup removes inline branching logic [3], and the connection sheet now leads with AWS account ID, then database, then optional description, so empty descriptions don't ghost-print as blank names [4]. CLI shipped beta.15 with a Realtime bump from v2.128.0 to v2.128.2 [6], while the stack refactor landed focused modules for workspace metadata and managed identity policy [5]. Evals refreshed latest results automatically [7].

Action items

References

  1. [1] feat(studio): show PrivateLink resource IDs and use connection copy ↗ supabase/supabase
  2. [2] fix(studio): clarify MFA backup authenticator copy ↗ supabase/supabase
  3. [3] feat(studio): extract PrivateLink status copy ↗ supabase/supabase
  4. [4] feat(studio): tighten PrivateLink sheet fields ↗ supabase/supabase
  5. [5] refactor(stack): simplify managed identity policy ↗ supabase/cli
  6. [6] v2.115.0-beta.15 ↗ supabase/cli
  7. [7] chore: refresh eval results ↗ supabase/evals

Quick answers

What shipped in Supabase on August 17, 2026?
Four linked PRs ship clarity to PrivateLink configuration and MFA backup flows, replacing ambiguous copy with resource IDs and clearer field ordering. In total, 11 commits, 12 pull requests, and 1 releases landed.
Who contributed to Supabase on August 17, 2026?
7 developers shipped this update, including Danny White, doublethink, jgoux, github-actions[bot], dependabot, supabase-evals-releaser, and supabase-evals-releaser[bot].
What were the notable Supabase updates?
feat(studio): show PrivateLink resource IDs and use connection copy, fix(studio): clarify MFA backup authenticator copy, and feat(studio): extract PrivateLink status copy.