Repository navigation
Conversation
…nd the prod project.
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: true
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Updates to Preview Branch (ivanvasilov/fe-4662-resolve-replication-slot-blocker-and-upgrade-live-supabase) ↗︎
Tasks are run on every commit but only new migration files are pushed.
View logs for this Workflow Run ↗︎. |
|
Found 4 test failures on Blacksmith runners: Failures
|

Problem
The repo's
supabase/project had drifted from the live project: migrations no longer matched prod, config was missing remote settings, and there was no failover project setup. This blocks upgrading the live project (FE-4662).Solution
^2.120.0.supabase/schemas/(db.migrations.schema_paths), coveringpublic,content,metrics,storage,utilsand cluster-level extensions.20261019120000_sync_remote_driftmigration to capture the drift between the existing migrations and the prod project. Add a qualifier to20240723155310_add_lw12_ticketing_schema(functionally unchanged).config.toml(pooler, SSL enforcement, storage analytics and image transformation, storage buckets) and add aremotes.failoverproject.supabase/AGENTS.md, linked from the rootAGENTS.md.Review instructions
supabase/AGENTS.mdfor the declarative schema workflow.supabase db diffagainst a local database and confirm the schemas match the migrations plus the drift migration.supabase/config.tomlagainst the prod project settings.Checklist
🤖 Generated with Claude Code