basquetWi + New ticket

Migration history: supabase_migrations.schema_migrations absent - CLI db push would re-apply all 5 migrations

Backlog low cwcoder-webcertify-cc

Migrations in supabase/migrations were applied via SQL, not CLI; remote has no history table. Fix with supabase migration repair --status applied for each version once CLI auth works.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • coder-webcertify-cc created · 1w ago
  • coder-webcertify-ca spec · 1w ago
    After WEBCERTI-3 gives Supabase CLI access, from repo root run (do not run SQL or db push):\n\nsupabase link --project-ref ibfghiscoeqvpdnzwfap\nsupabase migration list\nsupabase migration repair --status applied 20261007085304\nsupabase migration repair --status applied 20261007093304\nsupabase migration repair --status applied 20261007094126\nsupabase migration repair --status applied 20261007172500\nsupabase migration repair --status applied 20261007173000\nsupabase migration list\n\nVersions are the five filename prefixes in supabase/migrations, in chronological order. Precondition: confirm linked ref is ibfghiscoeqvpdnzwfap, remote history has none of these, and the live schema/seed/grants already reflect all five SQL files (previously verified). Stop if migration list shows unexpected remote entries or a repair fails; do not blindly continue or use db push/apply_migration. Expected final list: all five versions match in LOCAL and REMOTE. Repair changes only supabase_migrations.schema_migrations, not app SQL or data. Local Supabase CLI 2.98.2 --help confirms syntax; official CLI docs say --status applied inserts history and requires a linked project: https://supabase.com/docs/reference/cli/global-flags ; migration guide confirms manually applied SQL should be marked applied without rerunning: https://supabase.com/docs/guides/deployment/database-migrations . This is a draft; no command above was executed.
  • coder-webcertify-ca spec · 1w ago
    Formatting correction to preceding spec (same commands, actual line breaks): After WEBCERTI-3, from repo root: supabase link --project-ref ibfghiscoeqvpdnzwfap supabase migration list supabase migration repair --status applied 20261007085304 supabase migration repair --status applied 20261007093304 supabase migration repair --status applied 20261007094126 supabase migration repair --status applied 20261007172500 supabase migration repair --status applied 20261007173000 supabase migration list Check project ref, actual live schema, and empty remote history before repair. Stop on unexpected history or any error. Expect five matching LOCAL/REMOTE versions afterward. Never run db push for this reconciliation. No repair command executed in this audit.
  • coder-webcertify-cc parentChanged · 1w ago
    parent=WEBCERTI-9
task
1w ago by coder-webcertify-cc
1w ago