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-05-07
stories 102

© 2026 RepoJournal Home Showcase Explore How it works Privacy

$ the-wire · showcase

SUPABASE CUTS REACT 18 LOOSE, MOVES TO PRODUCTION-READY STACK

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

The platform ditched an archived MDX library and bumped vulnerable dependencies to unblock React 19 adoption across the entire dashboard.

Supabase migrated from the unmaintained `next-mdx-remote` to `next-mdx-remote-client` [1], a maintained fork that clears the path to React 19. The move hits both `apps/www` and supporting infrastructure, solving a critical blocker for modernizing the tech stack. In parallel, the team bumped core SDK dependencies across the workspace [2], tightening security posture and reducing build conflicts—standard hygiene that compounds over time. On the database side, Postgres 15.14.1.116 and 17.6.1.116 shipped with x86 variants [3][4][5], alongside new OrioleDB editions [6][7]. The dashboard picked up a timezone picker in the user dropdown [8], letting teams debug logs in their app's deployment region without touching OS settings—a quality-of-life win for cross-region ops. Realtime 2.92.2 landed a graceful shutdown fix [9] that prevents CDC RLS processes from hanging on connection errors [10], stopping cascading supervisor restarts. Smaller touch: contact email addresses moved from .io to .com [11] for legal, security, and abuse channels.

Action items

References

  1. [1] chore: migrate from `next-mdx-remote` to `next-mdx-remote-client` ↗ supabase/supabase
  2. [2] chore: Bump vulnerable dependencies (#45634) supabase/supabase ↗
  3. [3] 15.14.1.116 ↗ supabase/postgres
  4. [4] 17.6.1.116 ↗ supabase/postgres
  5. [5] 15.14.1.116-x86 ↗ supabase/postgres
  6. [6] 17.6.0.073-orioledb ↗ supabase/postgres
  7. [7] 17.6.0.073-orioledb-x86 ↗ supabase/postgres
  8. [8] feat(studio): add timezone picker to user dropdown ↗ supabase/supabase
  9. [9] v2.92.2 ↗ supabase/realtime
  10. [10] fix: gracefully stop on connect error for cdc rls processes ↗ supabase/realtime
  11. [11] Update www contact us page email addresses from io to com domain (#45616) supabase/supabase ↗

Quick answers

What shipped in Supabase on May 7, 2026?
The platform ditched an archived MDX library and bumped vulnerable dependencies to unblock React 19 adoption across the entire dashboard. In total, 48 commits, 46 pull requests, and 8 releases landed.
Who contributed to Supabase on May 7, 2026?
3 developers shipped this update, including djhi, jordienr, and edgurgel.
What were the notable Supabase updates?
chore: migrate from `next-mdx-remote` to `next-mdx-remote-client`, chore: Bump vulnerable dependencies (#45634), and 15.14.1.116.