I agree but I also have migrations that don't correspond to any release of the product. You need to run a migration to update your database so you can test you

I agree but I also have migrations that don't correspond to any release of the product. You need to run a migration to update your database so you can test your changes. A single product release might contain hundreds of migration files; maybe some that simply undo the affect of some previous migration. The pain of that is real but your point is valid. I like this product but I agree that it doesn't solve all migration issues. I do think we need better migration tools.