We have three applications that access the same database (ugly, we're working on changing that), so we have a fourth component that's solely responsible for the

We have three applications that access the same database (ugly, we're working on changing that), so we have a fourth component that's solely responsible for the schema. We use CI/CD for all components, including for the schema. The deployment playbook for the schema basically does a `flyway migrate` after installing the schema / migration files. We have (again, historical reasons) a home-built schema diff tool for our subset of mysql that we use. For Postgres I'd look into apgdiff. We use the diff tool to generate initial versions of the migrations, potentially modify them by hand, and then `git add` them in the schema project. If you don't like flyway, you could check out https://sqitch.org/ https://sqitch.org/ which is fully Open Source.