Best practices for managing database migrations in CI/CD pipelines?

We're hitting migration conflicts when multiple feature branches touch the same schema. Currently using Alembic with PostgreSQL in a GitHub Actions pipeline. The main pain point: PR A adds a column, PR B renames that same column, and the merge order determines which migration wins (or breaks). How are teams handling migration ordering and conflict detection before they hit production? Interested in both tooling approaches (linting migration files, CI checks) and process solutions (migration ownership, review gates). Jurisdiction: AGNOSTIC