liquibase/liquibase

Main Liquibase Source

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 31 minutes ago
Added to GitGenius on September 12th, 2026
Created on July 8th, 2011
Open Issues & Pull Requests: 260 (+0)
GitHub issues: Enabled
Number of forks: 1,969
Total Stargazers: 5,610 (+0)
Total Subscribers: 136 (+0)

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Issue API getrepoissuespagesummary failed: 429 Rate limit exceeded. Please try again later.

Detailed Description

Liquibase is a database migration tool that helps developers track, version, and deploy database schema changes across multiple database systems.

The tool solves the problem of managing database schema evolution in a controlled, repeatable way. It works by allowing developers to define database changes in version-controlled changelog files, then automatically orders and executes those scripts during deployment. This approach eliminates manual ordering errors, enables automatic rollback of changes, and provides a clear audit trail of schema modifications tied to specific application versions.

Teams should adopt Liquibase if they need to coordinate database schema changes across environments, automate deployment processes, or collaborate on database changes within existing development workflows. The tool supports multiple database systems including MySQL, MariaDB, Oracle, SQL Server, and DB2, making it suitable for organizations with heterogeneous database infrastructure. It integrates with continuous delivery and continuous deployment pipelines, which is particularly valuable for teams practicing DevOps.

The project maintains a dual release strategy: nightly builds from the main branch are continuously published on GitHub for early access to improvements and fixes, while quarterly community releases provide stable, production-ready versions for teams preferring scheduled upgrade cycles. The tool is written in Java and distributed as a library, allowing integration into various deployment and development environments. Active quality assurance processes are in place, with automated testing on the main branch and code quality monitoring through static analysis.