The Wire · Showcase
POSTGRES DROPS FOUR NEW BUILDS, STUDIO SHIPS STATE REFACTOR
By RepoJournal · Filed · About Supabase
Supabase shipped four Postgres variants overnight while Studio extracts SQL editor state from its god store, cutting architectural debt and making the dashboard faster to reason about.
The Postgres desk landed releases across three major versions: 17.6.1 [1], 17.6.0 with OrioleDB support [2], and 15.14.1 in both standard and PostgREST flavors [3][4], plus a combined OrioleDB-PostgREST build [5]. These track upstream Postgres security and stability fixes. On the Studio side, a major refactor extracted the SQL editor session store from the monolithic god store [7], isolating ephemeral state like query results and explain plans into their own mutation layer. This lands as part of a larger state re-layering effort that will make the editor easier to test and modify. Separately, the telemetry team plugged real gaps in creation-funnel tracking [8] that went live in June but had blind spots around error classification, confirmed against production PostHog data. The Monaco Editor also got standardized across all Studio environments [6], removing CDN loading and simplifying asset initialization. On infrastructure, the ETL team added a new `fix-pipeline` xtask [9] with commands to strip hostaddr fields and toggle DuckLake maintenance modes, plus cleaned up formatting scripts [10]. A ClickHouse serialization fix [11] prevents race conditions when parallel ctid copy workers collide on first-time table creation on Cloud.
Action items
- → Upgrade to Postgres 17.6.1 or 15.14.1 at your next deploy window supabase/postgres [plan]
- → Review Studio's SQL editor session store refactor if you maintain custom query tools supabase/supabase [monitor]
- → ETL users: test fix-pipeline xtask in local dev before production pipelines supabase/etl [monitor]
References
- [1] 17.6.1.142-x86 ↗ supabase/postgres
- [2] 17.6.0.099-orioledb-x86 ↗ supabase/postgres
- [3] 15.14.1.142-x86 ↗ supabase/postgres
- [4] 15.14.1.142-pgrst1414 ↗ supabase/postgres
- [5] 17.6.0.099-orioledb-pgrst1414-x86 ↗ supabase/postgres
- [6] chore: Remove CDN loading for the Monaco editor in all environments (#47182) supabase/supabase
- [7] refactor(studio): extract SQL editor session store from god store (#47349) supabase/supabase
- [8] feat(telemetry): fix creation-funnel tracking gaps (#47386) supabase/supabase
- [9] feat(xtask): add fix-pipeline command ↗ supabase/etl
- [10] ref(scripts): remove fmt shell scripts ↗ supabase/etl
- [11] fix(clickhouse): serialise first-time table creation across ctid copy workers ↗ supabase/etl
FAQ
- What changed in Supabase on July 1, 2026?
- Supabase shipped four Postgres variants overnight while Studio extracts SQL editor state from its god store, cutting architectural debt and making the dashboard faster to reason about.
- What should Supabase teams do about it?
- Upgrade to Postgres 17.6.1 or 15.14.1 at your next deploy window • Review Studio's SQL editor session store refactor if you maintain custom query tools • ETL users: test fix-pipeline xtask in local dev before production pipelines
- Which Supabase repositories shipped on July 1, 2026?
- supabase/postgres, supabase/supabase, supabase/etl