liquibase ORG

139 repos
221 followers
0 following

Java 61%
Shell 8%
Groovy 6%
PLpgSQL 6%
Go 3%

Liquibase > Note: This repository's default branch is main. > - Local clones/forks: run git branch -m master main && git fetch origin && git branch -u origin/main main >…

Liquibase ![Build and Test](https://github.com/liquibase/liquibase/actions/workflows/run-tests.yml) ![Nightly Release](https://github.com/liquibase/liquibase/releases/tag/nightly) ![Quality Gate Status](https://sonarcloud.io/summary/new_code?id=liquibase)

> Note: This repository's default branch is main.
> - Local clones/forks: run git branch -m master main && git fetch origin && git branch -u origin/main main
> - CI / scripts / docs: update any references to master (e.g., raw.githubusercontent.com/liquibase/liquibase/master/..., workflow triggers, submodules) to use main

Liquibase helps millions of developers track, version, and deploy database schema changes. It will help you to:

Control database schema changes for specific versions
Eliminate errors and delays when releasing databases
Automatically order scripts for deployment
Easily rollback changes
Collaborate with tools you already use

This repository contains the main source code for Liquibase Community. For more information about the product, see the Liquibase website.

Release Cadence and Access

At Liquibase, we believe great database change management starts with a community that can rely on a predictable and transparent release process. To support this commitment, and starting with version 5.0.2, we are providing two clear ways for the community to access updates and improvements:

Main Branch Builds on GitHub – Main branch builds are continuously published on GitHub, offering early access to the latest improvements and fixes as they are developed. These builds enable the community to test upcoming capabilities and provide feedback ahead of the next official release.
Quarterly Community Releases – Liquibase Community updates are released quarterly (Feb, May, Aug, Nov) providing stable, production-ready versions that allow teams to plan upgrades and maintenance with confidence. These releases are available through all standard distribution channels, including GitHub, Maven Central, package managers, container registries, and other official Liquibase Community distribution locations.

Together, these options ensure that teams can choose the path that best fits their needs - whether prioritizing stability through scheduled releases or engaging early with the latest innovations in Liquibase.

Build Access and Release Planning

Nightly builds: The latest Main branch build is available at https://github.com/liquibase/liquibase/releases/tag/nightly — download liquibase-nightly.tar.gz (Linux/macOS) or liquibase-nightly.zip (Windows). Updated automatically after each successful test run on main.
Latest Release: v5.0.3 — May 15, 2026 \

https://www.liquibase.com/download-community

Next Planned Release: August 20, 2026
Roadmap: \

https://github.com/orgs/liquibase/projects/3/views/9?layout=board

Liquibase Automation and Integrations

Liquibase Community has built-in support for a variety of databases. Databases that are not part of Liquibase Community require extensions that you can download for free. Here is the full list of supported databases.

Liquibase can be integrated with Maven, Ant, Gradle, Spring Boot, and other CI/CD tools. For a full list, see Liquibase Tools & Integrations. You can use Liquibase with GitHub Actions, Spinnaker, and many different workflows.

Install and Run Liquibase

System Requirements

Liquibase system requirements can be found on the Download Liquibase page.

An H2 in-memory database example for CLI

1. Download and run the appropriate installer. 2. Make sure to add Liquibase to your PATH. 3. Copy the included examples directory to the needed location. 4. Open your CLI and navigate to your examples/sql or examples/xml directory. 5. Start the included H2 database with the liquibase init start-h2 command. 6. Run the liquibase update command. 7. Run the liquibase history command to see what has executed!

See also how to get started with Liquibase in minutes or refer to our Installing Liquibase documentation page for more details.

Docker

The official Liquibase Community Docker images are built from the [docker/](docker/) directory of this repository and published to Docker Hub, GitHub Container Registry, and Amazon ECR Public:

bash
docker pull liquibase/liquibase

See the [Docker README](docker/README.md) for tags, usage, and examples, and file Docker image issues in this repository. The images were previously maintained in the now-deprecated liquibase/docker repository.

The commercial liquibase/liquibase-secure image is maintained internally by Liquibase — contact Liquibase Support for issues.

Documentation

Visit the Liquibase Documentation website to find the information on how Liquibase works.

Courses

Learn all about Liquibase by taking our free online courses at Liquibase University.

Want to help?

Want to file a bug or improve documentation? Excellent! Read up on our guidelines for contributing!

Contribute code

Use our step-by-step instructions for contributing code to the Liquibase project.

Join the Liquibase Community

Earn points for your achievements and contributions, collect and show off your badges, add accreditations to your LinkedIn. Learn more about the pathway to Legend and benefits. Enjoy being part of the community!

Liquibase Extensions

Provide more database support and features for Liquibase.

License

Liquibase Community is licensed under the Functional Source License (FSL).

Liquibase Secure has additional features and support and is commercially licensed.

LIQUIBASE is a registered trademark of Liquibase Inc.

Contact us

Liquibase Forum

Liquibase Blog

Get Support & Advanced Features

Publish Release Manual Trigger to Sonatype

1. When a PO (Product Owner) or a Team Leader navigates to Publish a release from here -> https://github.com/liquibase/liquibase/releases/, the workflow from /workflow/release-published.yml job is triggered.
2. When a release is triggered, the workflow file will stop after Setup step and an email will be sent out to the list of approvers mentioned in job manual_trigger_deployment. You can click on the link and perform anyone of the options mentioned in description.
3. A minimum of 2 approvers are needed in order for the other jobs such as deploy_maven, deploy_javadocs, publish_to_github_packages, etc to be executed.
4. When you view the GitHub PR, make sure to verify the version which is being published. It should say something like Deploying v4.20.0 to sonatype

All public repos (139)

Show forks Show archived

More creators on gitmyhub

octocat mitchellh defunkt programthink xiaolai