Problem
pickforge-pro-dev has the expected schema migrations, but most were applied with generated remote timestamps that do not match the canonical filenames in supabase/migrations/.
supabase db push --linked --dry-run therefore refuses before evaluating new migrations because the remote history contains versions absent locally.
Observed while deploying #34. The new 20260712193633_checkout_deletion_lifecycle migration was applied and recorded with its canonical version, so the deployed lifecycle is not blocked.
Impact
Future routine supabase db push deployments remain blocked unless the historical version mapping is reconciled. Direct single-file execution is currently required.
Suggested next action
- Compare the remote generated versions with their canonical local migration equivalents.
- Choose one canonical migration-history strategy.
- Repair history without re-running already-applied DDL.
- Prove
supabase db push --linked --dry-run reports no historical mismatch.
Severity: maintenance / deployment reliability; does not block current test-mode validation.
Source: #34 deployment.
Problem
pickforge-pro-devhas the expected schema migrations, but most were applied with generated remote timestamps that do not match the canonical filenames insupabase/migrations/.supabase db push --linked --dry-runtherefore refuses before evaluating new migrations because the remote history contains versions absent locally.Observed while deploying #34. The new
20260712193633_checkout_deletion_lifecyclemigration was applied and recorded with its canonical version, so the deployed lifecycle is not blocked.Impact
Future routine
supabase db pushdeployments remain blocked unless the historical version mapping is reconciled. Direct single-file execution is currently required.Suggested next action
supabase db push --linked --dry-runreports no historical mismatch.Severity: maintenance / deployment reliability; does not block current test-mode validation.
Source: #34 deployment.