I think making schema changes via migrations would be explicit and should lead to it being predictable. Maybe the best of both worlds is the ORM spitting out wh

I think making schema changes via migrations would be explicit and should lead to it being predictable. Maybe the best of both worlds is the ORM spitting out what it thinks the migration file should be based on the database schema and the new model changes? The migration process then runs the actions in the migration file. If it fails in new environments this is telling that something is different in that environment and needs to be investigated.