$ the-wire · showcase
CLI DECLARATIVE APPLY NOW PROVISIONS SUPABASE PLATFORM SCHEMA AUTOMATICALLY
By RepoJournal · Filed · About Supabase · Composed from the cited sources · methodology
![supabase-libs-pr-manager[bot]](https://avatars.githubusercontent.com/u/54469796?v=4)
Supabase CLI just locked down a critical fix for shadow database migrations: the declarative apply path now provisions auth, storage, and realtime schemas before your custom migrations run, eliminating the dependency resolution failures that have been breaking migrations for weeks.
The CLI team shipped two related fixes [1] [2] that solve the same underlying problem: without the platform baseline provisioned first, declarative schemas couldn't resolve Supabase-managed dependencies during apply or cache warmup. This was a silent killer for teams using shadow databases with auth-dependent migrations. The follow-up fix [2] closes a gap in the `generate` to `sync` handoff that the original PR left open. Meanwhile, the team also automated the Management API sync workflow [3] to catch upstream OpenAPI changes hourly and open PRs when regeneration is needed, keeping `@supabase/api` in sync without manual intervention. On the database layer, Supavisor shipped a meaningful performance win [4]: prepared statement eviction switched from random to LRU, which means hot statements stay hot instead of getting evicted with cold ones and forcing expensive Parse round-trips. For auth, Supavisor [5] standardized credential comparison to use `secure_compare` everywhere, closing an inconsistency that existed in password auth. Realtime cleaned up its test suite [6] by removing unsupported e2e features and fixing test cleanup that was causing cross-test pollution, and bumped supabase-js to v2.108.0 [7] which includes a consistent resend flow for auth confirmations.
Action items
- → If you're using declarative migrations with shadow databases, pull the latest CLI immediately to get the platform baseline fix supabase/cli [immediate]
- → Review your prepared statement patterns in high-throughput Postgres connections; Supavisor's LRU eviction means you should see fewer Parse round-trips supabase/supavisor [monitor]
- → Update supabase-js to v2.108.0 in dependent projects for the auth resend consistency fix supabase/realtime [plan]
References
- [1] feat(cli): set up platform baseline before declarative apply (#5515) ↗ supabase/cli
- [2] fix(cli): provision platform baseline in declarative baseline catalog (#5521) ↗ supabase/cli
- [3] chore(ci): add API package sync workflow ↗ supabase/cli
- [4] perf(db_handler): use LRU eviction for backend prepared statements ↗ supabase/supavisor
- [5] fix(auth): use secure_compare for credential comparisons ↗ supabase/supavisor
- [6] chore: remove e2e unsupported features ↗ supabase/realtime
- [7] chore: update @supabase/supabase-js to v2.108.0 ↗ supabase/realtime
