Skip to content

v0.158.3: chore(db): capture authoritative Cloud schema baseline for self-host migration

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Jun 19:04
v0.158.3
3556fd9

chore(db): capture authoritative Cloud schema baseline for self-host migration

What

Authoritative snapshot of the live production schema (Cloud zmlluqqqwrfhygvpfqka, PG 17.6), captured 2026-06-22 as the source of truth for the Cloud → self-host migration. Prod had drifted from the repo migration chain (renames, type changes, out-of-band MCP DDL), so a dump of prod — not a replay of migrations/ — is the truth.

  • supabase/baseline/cloud_schema_2026-06-22.sql — public schema via pg_dump --schema-only: 62 tables, 50 functions, 20 enum types, 199 RLS policies, 46 triggers, 213 indexes.
  • supabase/baseline/cloud_auth_hooks_2026-06-22.sql — the auth.users → handle_new_user trigger (cross-schema; a public-only dump misses it, which would silently break signup/invite profile creation).
  • supabase/baseline/README.md — provenance, load order for the new prod stack, and deliberate exclusions (data, platform-managed schemas/triggers).

Why

Doubles as the P1 load artifact for the new dedicated self-hosted prod stack. No app code; no change to any running database.

🤖 Generated with Claude Code

Full Changelog: v0.158.2...v0.158.3
Merged PR: #516

Assets 2
Loading