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

REALTIME CUTS TEST FLAKINESS, SUPABASE FIXES EXPERIMENT BUCKETING

By RepoJournal · Filed · About Supabase

Supabase shipped fixes to two critical infrastructure problems overnight: realtime's e2e tests now run reliably across regions, and a PostHog experiment flag was reading wrong bucketing data across the entire platform.

The realtime team crushed a major test stability issue [1] that was dropping broadcast events into unestablished subscriptions and breaking concurrent insert filters with race conditions. They raised Phoenix channel join timeouts to 10 seconds for APAC replay channels, then swapped out flaky ID-based filtering for UUID comparisons. This hits the team hard: unreliable tests mean you can't trust your deployments. The fix clears the path to ship with confidence again. On the main repo, engineers merged a critical experiment flag fix [2] that made the dataApiRevokeOnCreateDefault PostHog flag reads shape-agnostic instead of multivariate. The flag was bucketing correctly (treatment split reconciled to 2.56% vs expected 2.5%), but control users were invisible to the system. That means every experiment using this flag has been blind to half its data. In lighter news, billing updated storage pricing math [3] to account for month-length variance. The difference between 744-hour and 730-hour months was creating a 1.5% pricing drift. It's a small fix, but billing caught it and cleaned it up.

Action items

References

  1. [1] chore: reduce e2e flakiness ↗ supabase/realtime
  2. [2] fix(experiment): make dataApiRevokeOnCreateDefault flag reads shape-agnostic ↗ supabase/supabase
  3. [3] chore(pricing-www): adjust storage prices ↗ supabase/supabase

FAQ

What changed in Supabase on May 24, 2026?
Supabase shipped fixes to two critical infrastructure problems overnight: realtime's e2e tests now run reliably across regions, and a PostHog experiment flag was reading wrong bucketing data across the entire platform.
What should Supabase teams do about it?
Merge the realtime e2e flakiness fix before your next test run • Audit any active experiments using dataApiRevokeOnCreateDefault - control bucket data was lost • Update pricing displays to reflect new storage month-length math
Which Supabase repositories shipped on May 24, 2026?
supabase/realtime, supabase/supabase

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.