Database migrations run as a separate pipeline triggered when migration files change. It deploys to staging first, then to production with manual approval — ensuring safe, staged rollouts. This is critical because database changes can't be rolled back as easily as code deployments.