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

CLI DECLARATIVE APPLY NOW PROVISIONS SUPABASE PLATFORM SCHEMA AUTOMATICALLY

By RepoJournal · Filed · About Supabase

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.

One email a day. Unsubscribe in one click.

Action items

References

  1. [1] feat(cli): set up platform baseline before declarative apply (#5515) supabase/cli
  2. [2] fix(cli): provision platform baseline in declarative baseline catalog (#5521) supabase/cli
  3. [3] chore(ci): add API package sync workflow ↗ supabase/cli
  4. [4] perf(db_handler): use LRU eviction for backend prepared statements ↗ supabase/supavisor
  5. [5] fix(auth): use secure_compare for credential comparisons ↗ supabase/supavisor
  6. [6] chore: remove e2e unsupported features ↗ supabase/realtime
  7. [7] chore: update @supabase/supabase-js to v2.108.0 ↗ supabase/realtime

Quick answers

What shipped in Supabase on June 10, 2026?
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. In total, 15 commits, 16 pull requests, and 8 releases landed.
Who contributed to Supabase on June 10, 2026?
5 developers shipped this update, including jgoux, MorganaFuture, Snehil-Shah, filipecabaco, and supabase-libs-pr-manager[bot].
What were the notable Supabase updates?
feat(cli): set up platform baseline before declarative apply (#5515), fix(cli): provision platform baseline in declarative baseline catalog (#5521), and chore(ci): add API package sync workflow.

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?