opschain server migrate list
Included from Basic tier
Lists the binary's migrations with their per-version ledger verdict —
applied, pending, mismatched, assumed backfill — directly from the
configured database, without any server process. Read-only, and the output
shape is identical to opschain admin database migrations list, so
runbooks can cite either.
The store comes from the server host's own config.yaml (resolved via
--home). A version the database applied but this binary does not carry
lists as unknown — the database was migrated by a newer build, which is
exactly what to know before pointing an older binary at it.
Exit codes
| Code | Meaning |
|---|---|
| 0 | The list printed. |
| 1 | The database was unreachable or holds no migration history. |
| 2 | Usage error — no config.yaml at the resolved server home. |
Examples
opschain server migrate list
opschain server migrate list -o json
See also
opschain docs cli/server-migrate-status— the verdict with exit-code semantics for scripts and runbooks.