The Wire · Showcase
WRAPPERS TIGHTENS MYSQL HANDLING, STUDIO COMPLETES STATE MIGRATION, ETL CUTS SCHEMA CLONES BY 30%
By RepoJournal · Filed · About Supabase
Supabase shipped production fixes across three critical systems overnight: wrappers now sanitizes MySQL errors and handles text columns correctly, the Studio SQL editor finally kills its compatibility layer after migrating 23 consumers, and the ETL pipeline cut row-decoding latency by a third.
The wrappers team released v0.2.1 [1] with MySQL hardening that sanitizes error details to prevent information leakage and adds support for varchar and bpchar columns that were breaking text field queries. That same release kicked off the OpenAPI FDW deployment pipeline [2], already live on pro tier. Over in Studio, the SQL editor state refactor that started weeks ago finally shipped [3]: all 23 internal consumers of the facade layer now import directly from the real state module, deleting the compatibility shims that slowed iteration. The ETL team went deep on performance, cutting schema lookup latency 30% [6] by moving the ReplicatedTableSchema out of the cloned SharedTableState to avoid redundant clones during row decoding. They also ported critical shell scripts into native Rust [4] [5], replacing migrate, clickhouse test, MSRV, and init tasks with cargo x commands that integrate better with the build system and give CI cleaner output.
Action items
- → Deploy wrappers v0.2.1 to your wrapped MySQL instances if you use varchar or bpchar fields supabase/wrappers [plan]
- → Update your Studio import paths from @/state/sql-editor-v2 to @/state/sql-editor/sql-editor-state if you maintain custom extensions supabase/supabase [plan]
- → Monitor ETL row throughput after the schema clone optimization rolls to your replication cluster supabase/etl [monitor]
References
- [1] wasm_openapi_fdw_v0.2.1 ↗ supabase/wrappers
- [2] docs(openapi): update checksum for version 0.2.1 ↗ supabase/wrappers
- [3] refactor(studio): import SQL editor store from source, delete facade + barrel (#47533) supabase/supabase
- [4] feat(scripts): port migrate and clickhouse test tasks ↗ supabase/etl
- [5] feat(scripts): cargo x msrv and init tasks ↗ supabase/etl
- [6] Avoid an extra schema clone during row decoding (#868) supabase/etl
FAQ
- What changed in Supabase on July 3, 2026?
- Supabase shipped production fixes across three critical systems overnight: wrappers now sanitizes MySQL errors and handles text columns correctly, the Studio SQL editor finally kills its compatibility layer after migrating 23 consumers, and the ETL pipeline cut row-decoding latency by a third.
- What should Supabase teams do about it?
- Deploy wrappers v0.2.1 to your wrapped MySQL instances if you use varchar or bpchar fields • Update your Studio import paths from @/state/sql-editor-v2 to @/state/sql-editor/sql-editor-state if you maintain custom extensions • Monitor ETL row throughput after the schema clone optimization rolls to your replication cluster
- Which Supabase repositories shipped on July 3, 2026?
- supabase/wrappers, supabase/supabase, supabase/etl