Liquibase

Track schema changes and execute only changesets that have not yet run

Changelogs can describe changes in XML, YAML, JSON, or SQL, and Liquibase compares them with its database-side history. It identifies unapplied changesets for each environment, executes them in order, and brings diff generation and rollback into the same change-management workflow.

Sources: [1]

Fits teams that want database changes in a repeatable release pipeline

It suits teams that review one change history across development, test, and production and automate it alongside application delivery. It is also a candidate for organizations supporting multiple database products or integrating change management with Maven, Gradle, Spring Boot, GitHub Actions, and similar tooling.

Sources: [1]

Review version 5 licensing and driver packaging before adoption

Liquibase Community 5 uses FSL-1.1-ALv2, which limits competing use and grants Apache-2.0 after two years. GitHub reports NOASSERTION for SPDX, so organizations should compare their intended use directly with the LICENSE text.

Version 5 Community distributions and containers no longer bundle database drivers or extensions by default. Add the required components with LPM or another documented method and keep credentials out of changelogs and logs. Release 5.0.4 also strengthens credential redaction and adds controls for changelog features that can execute code.

Sources: [3][2][4]