FACTUAL ACTIVITY RECORD · An activity record based on work that took place
Returning database migration to the standard Supabase CLI path
Removing custom connections and verifying production through link, history, dry-run, and application
Purpose
The first production migration stopped before changing the database because a custom psql preflight placed after Supabase CLI linking could not find a CA root. The path needed to rely only on the provider's standard connection and migration history.
Implementation
Direct psql, repository-managed CA material, custom TLS settings, and preflight/postflight SQL were removed from standard migration workflow. The sequence was standardized as supabase link, linked history inspection, the standard dry-run, migration application, then a second history inspection and dry-run.
standard migration workflow now statically checks the manual-run gate and standard CLI sequence while rejecting reintroduction of direct connections or CA management. Migration SQL and schema design were left unchanged.
Rendering diagram…
What was confirmed
Verification results
The earlier failure was confirmed to have occurred before any database change and to originate in the added direct connection rather than the standard CLI.
The initial migration was applied to production through the standard path, migration history matched, and the second dry-run found no pending migration.
The Dashboard check covered initial schemas, ACLs, and default privileges, and the Data API exposure was corrected to api only.
Basis for completion
Completion required a successful production run through the standard CLI sequence, matching history, zero pending migrations, and confirmation of the initial database boundary.