At work, I introduced the concept of automated migrations (as opposed to "let's do it by hand" and "stored procedures are a great solution") with Flyway. It has been a great success, even though the project needed to support multiple databases, which Flyway does not handle (but its API is easy to work with).
I'm not entirely sure of what it does with out-of-order migrations (eg, "master' has migration A,B,C, and "legacy" has had A and C backported - I'm not sure if Flyway will gracefully apply B on a "legacy" database when switching it to "master"), and the docs do not seem to mention this use case.
I'm not entirely sure of what it does with out-of-order migrations (eg, "master' has migration A,B,C, and "legacy" has had A and C backported - I'm not sure if Flyway will gracefully apply B on a "legacy" database when switching it to "master"), and the docs do not seem to mention this use case.