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.
Action items
- → Upgrade Realtime to 2.112.3 immediately if you deployed the previous version supabase/realtime [immediate]
- → Update CLI to fix declarative sync hangs on schema operations supabase/cli [immediate]
- → Patch cloudflare-exporter DNS metrics bug in production supabase/cloudflare-exporter [immediate]
- → Review and apply the 10-item feature flag cleanup to your dashboard deployment supabase/supabase [plan]
References
- [1] v2.112.3 ↗ supabase/realtime
- [2] fix(cli): stop declarative sync hanging on edge-runtime container exit ↗ supabase/cli
- [3] fix(cli): align services version sources ↗ supabase/cli
- [4] fix(cli): suggest subcommand placement for misplaced flags ↗ supabase/cli
- [5] fix: use int for ipVersion in DNS analytics response ↗ supabase/cloudflare-exporter
- [6] Chore/clean up feature flags 300626 (#47429) supabase/supabase
- [7] Remove old redirect links in database section (#47426) supabase/supabase
- [8] fix(account): stop sb marker leaking into email toast (#47455) supabase/supabase
- [9] chore: prepare CODEOWNERS for group renaming (#47131) supabase/supabase
- [10] v2.9.10 ↗ supabase/supavisor
FAQ
- What changed 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.
- What should Supabase teams do about it?
- Upgrade Realtime to 2.112.3 immediately if you deployed the previous version • Update CLI to fix declarative sync hangs on schema operations • Patch cloudflare-exporter DNS metrics bug in production
- Which Supabase repositories shipped on July 2, 2026?
- supabase/realtime, supabase/cli, supabase/cloudflare-exporter, supabase/supabase, supabase/supavisor