RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Pick a date

  1. Sat 2 may
  2. Mon 4 may
  3. Tue 5 may
  4. Wed 6 may
  5. Thu 7 may
  6. Fri 8 may
  7. Sat 9 may
  8. Mon 11 may
  9. Tue 12 may
  10. Wed 13 may
  11. Thu 14 may
  12. Fri 15 may
  13. Sat 16 may
  14. Sun 17 may
  15. Tue 19 may
  16. Wed 20 may
  17. Thu 21 may
  18. Sat 23 may
  19. Sun 24 may
  20. Mon 25 may
  21. Tue 26 may
  22. Wed 27 may
  23. Thu 28 may
  24. Fri 29 may
  25. Sat 30 may
  26. Sun 31 may
  27. Mon 1 jun
  28. Mon 8 jun
  29. Tue 9 jun
  30. Today 10 jun

The Wire · Showcase

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

By RepoJournal · Filed · About Supabase

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

FAQ

What changed 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.
What should Supabase teams do about it?
Verify React 19 compatibility in your integration tests before upgrading next-mdx-remote • Deploy Realtime 2.92.2 to production to fix CDC RLS hang conditions • Update your contact form endpoints if you've hard-coded supabase.io legal addresses
Which Supabase repositories shipped on May 7, 2026?
supabase/supabase, supabase/postgres, supabase/realtime

Related across the cluster

For your repos

The showcase is a teaser.
Your wire is the product.

Same engine. Different stack. Below: what changes when the wire is yours.

Showcase wire

  • •14 famous open source orgs
  • •One wire per day
  • •Public, generic
  • •Read on the web, when you remember

Your wire

  • →Up to 1,500 of your repos - orgs, deps, vendors
  • →Morning and evening briefs
  • →Action items routed to your team
  • →Slack delivery, email, breaking-news CVE alerts

Want a hands-on demo first? Ask a current user for an invite link.