The Wire · Showcase
REALTIME SHIPS TENANT MIGRATIONS DEBUGGER, CLI FIXES FORK-BOMB BUG
By RepoJournal · Filed · About Supabase
Supabase realtime just gave you a way to rescue tenants stuck in bad database states without touching production, while the CLI team plugged a silent catastrophe that was hammering CI pipelines.
Realtime v2.96.0 [1] and v2.95.0 [2] ship a new tenant migrations dashboard [3] that lets you inspect, plan, and apply fixes to corrupt database states using pg-delta under the hood, all without auto-executing anything. This is the debugging tool you've been missing when migrations leave tenants in limbo. On the CLI front, a critical binary resolution bug [4] was silently fork-bombing CI when the supabase-go binary wasn't co-located with the shim, causing multi-minute hangs followed by SIGTERM. The fix discriminates between found and not-found states instead of falling back to the shim itself. Meanwhile, the CLI team also restored the --auth flag on legacy functions [5] that was being dropped by the TS proxy layer, and cleaned up unused rawProjectConfig plumbing [6]. In the dashboard, RLS testing got a pglite sandbox [8] so you can safely test mutations against a ephemeral database instead of your actual schema. The supabase/cli npm package is now a lightweight shim [7] with optional peer dependencies on the platform-specific @supabase/cli-* binaries. Telemetry cleanup [9] resolved 13 audit findings including dead event removal and property narrowing. Security-wise, realtime bumped cowlib [10] to patch a vulnerability, and wrappers updated wasmtime to 36.0.7 [11] to close dependabot alerts. ETL is hardening replication with durable progress tracking [12] that persists across restarts and resumes from the latest safe boundary.
Action items
- → Upgrade CLI immediately if it's on PATH in your CI - fork-bomb fix is critical [ref:15] supabase/cli [immediate]
- → Test the RLS sandbox in the dashboard for your mutation-heavy queries before production supabase/supabase [plan]
- → Review realtime v2.96.0 tenant migrations page if you manage multi-tenant deployments supabase/realtime [monitor]
- → Update wasmtime in wrappers to 36.0.7 to clear security alerts supabase/wrappers [plan]
References
- [1] v2.96.0 ↗ supabase/realtime
- [2] v2.95.0 ↗ supabase/realtime
- [3] feat(dashboard): tenant migrations page ↗ supabase/realtime
- [4] fix(cli): prevent fork-bomb when supabase-go binary is not found ↗ supabase/cli
- [5] fix(cli): restore --auth flag on legacy functions new proxy (#5254) supabase/cli
- [6] fix(cli): remove rawProjectConfig from ProjectContext (#5281) supabase/cli
- [7] chore: move packaged dependencies to dev dependencies ↗ supabase/cli
- [8] RLS Tester sandbox environment (#45839) supabase/supabase
- [9] chore(telemetry): clean up frontend event catalog ↗ supabase/supabase
- [10] fix: cowlib security update (#1878) supabase/realtime
- [11] chore: update wasmtime version to 36.0.7 ↗ supabase/wrappers
- [12] feat(core): Implement new durable progress ↗ supabase/etl
FAQ
- What changed in Supabase on May 19, 2026?
- Supabase realtime just gave you a way to rescue tenants stuck in bad database states without touching production, while the CLI team plugged a silent catastrophe that was hammering CI pipelines.
- What should Supabase teams do about it?
- Upgrade CLI immediately if it's on PATH in your CI - fork-bomb fix is critical [ref:15] • Test the RLS sandbox in the dashboard for your mutation-heavy queries before production • Review realtime v2.96.0 tenant migrations page if you manage multi-tenant deployments
- Which Supabase repositories shipped on May 19, 2026?
- supabase/realtime, supabase/cli, supabase/supabase, supabase/wrappers, supabase/etl