Can a Doctrine Migrations rollback ever be safe after a destructive schema change in production?
In a Symfony application using Doctrine Migrations, I am planning a release that includes a destructive schema change (dropping a column that existing code still reads). I want a rollback plan I can actually trust, but the more I look at how migrations work, the less clear the safe path is. My understanding is that doctrine:migrations:migrate with a target v
symfony