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

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.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] wasm_openapi_fdw_v0.2.1 ↗ supabase/wrappers
  2. [2] docs(openapi): update checksum for version 0.2.1 ↗ supabase/wrappers
  3. [3] refactor(studio): import SQL editor store from source, delete facade + barrel (#47533) supabase/supabase
  4. [4] feat(scripts): port migrate and clickhouse test tasks ↗ supabase/etl
  5. [5] feat(scripts): cargo x msrv and init tasks ↗ supabase/etl
  6. [6] Avoid an extra schema clone during row decoding (#868) supabase/etl

Quick answers

What shipped 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. In total, 34 commits, 34 pull requests, and 1 releases landed.
Who contributed to Supabase on July 3, 2026?
2 developers shipped this update, including burmecia and farazdagi.
What were the notable Supabase updates?
wasm_openapi_fdw_v0.2.1, docs(openapi): update checksum for version 0.2.1, and refactor(studio): import SQL editor store from source, delete facade + barrel (#47533).

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.