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-05-24
stories 6

© 2026 RepoJournal Home Showcase How it works Privacy

$ the-wire · showcase

REALTIME CUTS TEST FLAKINESS, SUPABASE FIXES EXPERIMENT BUCKETING

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

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.

Quick answers

What shipped 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. In total, 3 commits and 3 pull requests landed.
Who contributed to Supabase on May 24, 2026?
3 developers shipped this update, including filipecabaco, seanoliver, and juleswritescode.
What were the notable Supabase updates?
chore: reduce e2e flakiness, fix(experiment): make dataApiRevokeOnCreateDefault flag reads shape-agnostic, and chore(pricing-www): adjust storage prices.