.svg)
.svg){kind=icon}
Liquibase 5.0 is Coming
Liquibase is evolving to support developers at every stage, from open-source collaboration to mission-critical delivery.
Available Q3 2025.
Liquibase OSS. Reimagined.
The new distribution is modular. You choose what to install and when. No clutter. No bloat. Just a clean, focused core.
Extensions and drivers are no longer bundled. They’re available on demand through an official package manager.
Support, fixes, and documentation are increasingly led by the community. Liquibase provides the structure to keep them moving forward.
For mission-critical environments, there’s now a dedicated Pro experience. Built for scale. Designed for confidence.
This is Liquibase OSS, refactored. Built for developers. Ready for what’s next.
Two Experiences. Built with Purpose.
For Liquibase OSS
For developers who want autonomy, control, and a community-first experience.
For Liquibase Pro
For teams who need scale, reliability, and enterprise-grade support.
What to Do Next
For OSS Users
To use Pro-only features, OSS users must upgrade to Liquibase Pro
For Pro Customers
Pro customers will need to switch to new Pro distribution channels. For guidance, please contact your CSM.
Stay Connected to Learn More
Watch the webinar
Watch our webinar recording to get a walkthrough of the changes, learn what's coming, and hear the Q&A.
.svg){kind=icon}
Liquibase 4.32
Get the release notes.' to 'Liquibase 4.32 is available now. Access the release notes to learn about the updates.
FAQ
No, we are not removing any OSS features, just cleaning up the core. By taking out Pro components and rarely used extensions, like Snowflake, we’re making OSS leaner and easier to maintain. All the essential functionality stays the same.
No, we are not destabilizing OSS. It’s a core part of how we build Liquibase Pro. The OSS community works closely with our team to shape the future of the product, and that collaboration helps keep OSS stable, reliable, and valuable for everyone.
No, Liquibase Pro is built on top of Liquibase OSS, so they will stay aligned. Changes made to OSS (once accepted and verified) will be included in future Pro releases, and we aim to keep both versions working together.
Most existing OSS projects—especially those that integrate with Maven, Gradle, Ant, or SpringBoot—will be unaffected and continue to work as expected. However, if you're using Liquibase OSS through the CLI, Docker container, or Packages (RPM, DEB, Homebrew, etc.), or you're not already managing your database driver separately, you may need to start doing so manually, via Liquibase Package Manager (LPM), or by upgrading to Liquibase Pro.
Liquibase OSS and Pro will be two distinct distributions — they are not designed to be used interchangeably on the same changesets or environments as it introduces risk and inconsistency. Customers are responsible for verifying compatibility when using both in parallel. To reduce risk and simplify your pipeline, we strongly recommend standardizing on one version per environment.
We’re communicating what to expect well in advance to give our community time to understand what’s happening and make the appropriate plans necessary. We expect to make the official change in Q3 2025.
Questions? Talk to us!
.svg){kind=icon}
