The Wire · Showcase
ETL FIXES APPLY-WORKER RACE CONDITION DURING RESTARTS
By RepoJournal · Filed · About Supabase
Supabase's ETL engine plugged a critical coordination bug that could corrupt table ownership when workers restart mid-sync.
The apply-worker restart logic now checks for active table-sync coordination before processing new WAL entries [1], preventing the main worker from stealing ownership of tables still being synced. This closes a race condition that could cascade into stalled replication pipelines. Alongside that fix, ETL migrations were restructured into source and store-specific tracks [2], with reversible SQLx pairs and shared migration logic — cleaner architecture that matters for operators running custom pipeline setups. Over in the main platform, the Next.js framework got bumped to patch the latest vulnerabilities [3], and the studio began delegating default privilege revocation to the platform API [4] so CLI and Terraform flows get the same security posture without reimplementing logic. Component cleanup continues across the board: Card legacy components migrated out [5], Input fields converged to Shadcn [6], and Tailwind CSS configs centralized into a shared config package [7]. Realtime shipped v2.93.0 with exposed cowboy dynamic buffer tuning [8], giving operators finer control over connection handling under load.
Action items
- → Deploy ETL fix [ref:1] before the next sync restart or table ownership event supabase/etl [immediate]
- → Upgrade Next.js in www app [ref:6] to resolve the security vulnerability supabase/supabase [plan]
- → Test Realtime v2.93.0 [ref:11] in staging if you manage high-concurrency websocket loads supabase/realtime [monitor]
References
- [1] fix(core): Fix missing catchup handling during restart ↗ supabase/etl
- [2] ref(migrations): Improve docs and migrations ↗ supabase/etl
- [3] chore: Bump `next` in `www` app (#45701) supabase/supabase
- [4] [FE-3145] feat(studio): use data_api_revoke_default_privileges flag (#45683) supabase/supabase
- [5] chore: migrate/remove Card_legacy_ (#45680) supabase/supabase
- [6] chore: migrate `Input` usages to Shadcn component in various screens/components (#45604) supabase/supabase
- [7] chore: Migrate all apps to use Tailwind CSS configs (#45530) supabase/supabase
- [8] v2.93.0 ↗ supabase/realtime
FAQ
- What changed in Supabase on May 8, 2026?
- Supabase's ETL engine plugged a critical coordination bug that could corrupt table ownership when workers restart mid-sync.
- What should Supabase teams do about it?
- Deploy ETL fix [ref:1] before the next sync restart or table ownership event • Upgrade Next.js in www app [ref:6] to resolve the security vulnerability • Test Realtime v2.93.0 [ref:11] in staging if you manage high-concurrency websocket loads
- Which Supabase repositories shipped on May 8, 2026?
- supabase/etl, supabase/supabase, supabase/realtime