RepoJournal
Supabase

@supabase

The open-source Firebase alternative powering thousands of startups

Keep up with Supabase in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

One email a day. Unsubscribe in one click.

Pick a date

Topics: JavaScript Full archive →

The Wire · Showcase

REALTIME REVERTS DEPENDENCIES, CLI FIXES DECLARATIVE SYNC HANGS

By RepoJournal · Filed · About Supabase

Realtime 2.112.3 pulled back a dependency change that broke something quietly enough to need a fast revert, while the CLI team crushed two nasty bugs that were silently killing schema syncs and DNS metrics.

Realtime [1] reverted dependencies to the previous stable version after a recent update introduced regressions, shipping 2.112.3 to get production back on track. The CLI team landed three critical fixes: one that stops declarative sync hanging indefinitely after shadow-database work completes [2], another that aligns service version sources so local CLI runs match actual stack deployments [3], and a third that surfaces better error messages when flags are misplaced in the command tree [4]. Meanwhile, Supabase core shipped a 10-item feature flag cleanup [6] that finally makes timezone selection always available after 3 months of gradual rollout, cleaned up stale database menu redirects [7], and squashed an auth toast bug where the sb marker was leaking into email confirmations [8]. The infrastructure team is preparing for a GitHub group rename from supabase/infra to supabase/platform [9]. Over in monitoring, cloudflare-exporter [5] had a silent killer: ipVersion was typed as string when GraphQL returns an integer, so DNS metrics were dying on every pod restart while tests never caught it because they bypassed JSON unmarshaling. Supavisor 2.9.10 added a dead port sweeper [10] to keep connection pools clean.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] v2.112.3 ↗ supabase/realtime
  2. [2] fix(cli): stop declarative sync hanging on edge-runtime container exit ↗ supabase/cli
  3. [3] fix(cli): align services version sources ↗ supabase/cli
  4. [4] fix(cli): suggest subcommand placement for misplaced flags ↗ supabase/cli
  5. [5] fix: use int for ipVersion in DNS analytics response ↗ supabase/cloudflare-exporter
  6. [6] Chore/clean up feature flags 300626 (#47429) supabase/supabase
  7. [7] Remove old redirect links in database section (#47426) supabase/supabase
  8. [8] fix(account): stop sb marker leaking into email toast (#47455) supabase/supabase
  9. [9] chore: prepare CODEOWNERS for group renaming (#47131) supabase/supabase
  10. [10] v2.9.10 ↗ supabase/supavisor

Quick answers

What shipped in Supabase on July 2, 2026?
Realtime 2.112.3 pulled back a dependency change that broke something quietly enough to need a fast revert, while the CLI team crushed two nasty bugs that were silently killing schema syncs and DNS metrics. In total, 39 commits, 41 pull requests, and 6 releases landed.
Who contributed to Supabase on July 2, 2026?
3 developers shipped this update, including avallete, jgoux, and shreekarshetty.
What were the notable Supabase updates?
v2.112.3, fix(cli): stop declarative sync hanging on edge-runtime container exit, and fix(cli): align services version sources.

More from @supabase

Daily updates, in your inbox

Follow Supabase

Keep up with Supabase in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.

or

One email a day. Unsubscribe in one click. Read a past issue →

Elsewhere on the wire

Want every project, not just this one?

We use privacy-friendly analytics (Google Analytics, IP-anonymized) to see which pages help readers. No ads, and we never sell your data. See our Privacy Policy.