Migrations are immutable. We run them once, and then they're done for good. The idea that migrations are reversible
- the "up" and "down" pattern that you find in, for example, Rails and Phoenix - is not something you should build a workflow on. Rolling back migrations should happen only when you made a mistake in a migration & need to revert the database and it's data to a previous schema version.