Skip to main content
Use migrations when you need to know what has been applied and what is still pending. The command compares migration files on disk with versions recorded in a target database history table. Without a database URL, it still lists disk files.

​
Use this when

  • A deploy needs a preflight view of pending files.
  • A branch may have ghost or out-of-order migrations.
  • Supabase local and remote histories need comparison.
  • sync refused and you need the history reason.

​
Run it

​
Flags

​
path
Directory containing numbered migration files.
​
url
Target database whose applied history should be compared.
​
schema.table
Migration history table. Use this for non-Supabase runners.
​
boolean
Print the reconciliation report as JSON.

​
Status values

Resolve ghost and out-of-order states before running sync.

Sync

Apply pending migrations after target reconciliation and safety gates.

Supabase integration

Configure Supabase paths, managed schemas, and runner targets.

Explain

Decode migration diagnostics.

CI gate

Add history checks before deploy.
Last modified on June 18, 2026