How sure are you that all changes deployed to your downstream environments, such as QA and Production, have been made via Flyway? If there are changes that have been applied directly to your downstream environments, such as production hotfixes, you are taking the following risks. 

1. Your migration scripts are validated against dev and test servers, but because our downstream environments are in a different state, they could fail on your next deployment. 
2. If there are changes made in production that haven't been back ported to dev and test, this invalidates the tests executed by your developers and QA teams as they have been run against an incorrect state.

To solve this problem, we are adding a database drift check into Flyway Pipelines for Flyway Community users which will alert you if any out of process changes have happened since your last deployment to prevent any surprises.  Flyway Pipelines you record and inform you if your database has drifted so you can investigate what the change is to ensure it is safe to deploy your next Flyway Migration. 

If you want to be made aware when this feature is released in Flyway Pipelines, please leave your email here.