opschain admin database migrations list
Included from Basic tier
Lists the server binary's embedded migrations against the migration ledger —
a GET to /api/admin/database/migrations. Each row is one migration version
with its verdict:
| State | Meaning |
|---|---|
applied | Applied, and the ledger's recorded name + content hash match this binary's migration. |
applied (assumed) | Applied before the ledger existed and backfilled from the binary's set — verified by name only, since the historical content cannot be proven. |
pending | Not yet applied (including a hole below the maximum applied version — the DETAIL column says so). |
mismatched | Recorded with a different name or content hash than this binary carries — the renumbered/edited-migration signal; the DETAIL column names what was recorded. |
unknown | A ledger row for a version this binary does not carry — the database was migrated by a newer build. |
Flags
| Flag | Meaning |
|---|---|
--server <url> | Server base URL (default: the active context / OPSCHAIN_SERVER). |
--auth-token <token> | Admin bearer token override (default: your opschain login session, then $OPSCHAIN_ADMIN_TOKEN, then the token stored by opschain admin login). |
Output is the table above — or the response document under -o json /
-o yaml.
Exit codes
| Code | Meaning |
|---|---|
| 0 | The list was fetched and rendered. |
| 1 | Request failed, non-2xx response, or the token was rejected. |
| 2 | Usage error — no server or no credential resolvable. |
Examples
opschain admin database migrations list
opschain admin database migrations list -o json
See also
opschain docs cli/admin-database-migrations-status— the pass/fail verdict the boot verification computes.