Migrations Panel
A database migrations timeline with a header and apply action above a railed list of pending migrations and applied ones with run times.
A database migrations timeline with a header and apply action above a railed list of pending migrations and applied ones with run times.
Search blocks by description or jump to a page.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Migrations Panel is the schema history surface for the primary Postgres database, split into a pending queue and an applied timeline on a shared rail. The header pairs a production chip with an Apply 2 pending button. Two pending migrations lead the list, each a dashed marker with a filename, a pending badge, a Preview SQL action, and a summary: one adds covering indexes for the invoice list and export queries, the other backfills total_cents on older invoices. Beneath them, four applied migrations render as compact rows with a filled check, the applied timestamp, a duration from 38 ms to 1.2 s, and the actor, either deploy bot or a named engineer.
Pending and applied migrations are separate typed const arrays, and the connecting rail is an absolutely positioned span drawn behind each marker. The final applied row omits the rail so the timeline closes cleanly.
Reach for this block on a database or developer tools page, wired to your migration runner. Keep the pending list ordered and let the Apply button run the batch in a single transaction, so a failure halfway through rolls the whole set back rather than leaving the schema split.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the pending and applied schema view. Other migration shapes:
Tip: state that the batch runs in one transaction; it is what lets an engineer apply pending work without fear of a half migrated schema.