Source code
Releases
Stability
DB migration runs in the same step as server start
Part of the Production readiness check · fix arrives as a guide
What it is
Database migrations run as part of the application start command rather than as a separate deploy step.
Why it matters
A failed migration now fails startup, so the platform restarts, retries the migration, and fails again — taking the fleet down rather than one step. With multiple instances they also race, each trying to migrate simultaneously.
How to fix it
Run migrations as a distinct release step that completes before new instances start, and take an advisory lock so concurrent runners serialise. Keep the app's start command doing nothing but starting the app.
Run them all on your app
Connect your repo and your live services with read-only scopes. The first scan is free, and nothing changes without your approval.