The Gap Between Database Version Control and Release Management

If you've been using Liquibase or Flyway for a while, you already know they solve a real problem. Migrations are tracked. Schema changes are repeatable. Your database evolves in lock-step with your application code. So why does deploying a database change still feel fragile? We asked ourselves the same question. We were running Liquibase in production across multiple environments, with a reasonably mature pipeline. Migrations were clean. The versioning worked. But the release — the actual act of getting a change from dev to test to production, with confidence — still had gaps we were plugging with shell scripts, spreadsheets, and hope. This is the problem drm-cli was built to solve. What Liquibase and Flyway Actually Do Let's be precise here, because nothing in this post is a criticism of either tool. Liquibase and Flyway are excellent. We still use them. What they do: track and apply schema changes. Given a target database and a set of migrations, they work out which changes haven't b