Liquibase Secure End of Life (EOL) Dates and End of Support (EOS) Dates
Liquibase Secure end of life (EOL) and end of support (EOS) dates: 2 Liquibase Secure versions have reached EOL, including Liquibase Secure 4.30 (EOL date: Nov 05, 2026) — no longer receiving security updates or patches. Liquibase Secure 4.31 reaches its End of Support date on Feb 17, 2027 — plan your upgrade path now. Liquibase Secure 6.0.2 is the current supported release, with support through Nov 17, 2028 — 6 versions in active support. Also see Graylog end of support life for related end-of-life information.
Currently Supported Liquibase Secure Releases - Active EOS/EOSL Support (6)
| Release | Released | Technical Support | Fixes | Latest |
|---|---|---|---|---|
| 6.0 | (1 month and 3 weeks ago) | (in 1 year and 11 months) | Active | 6.0.2 (5 days ago) |
| 5.2 | (5 months ago) | (in 1 year and 8 months) | (1 month and 3 weeks ago) | 5.2.2 (3 months ago) |
| 5.1 | (9 months ago) | (in 1 year and 4 months) | (5 months ago) | 5.1.1 (7 months ago) |
| 5.0 | (1 year and 1 month ago) | (in 1 year) | (9 months ago) | 5.0.3 (11 months ago) |
| 4.33 | (1 year and 4 months ago) | (in 7 months) | (1 year and 1 month ago) | 4.33.0 (1 year and 4 months ago) |
| 4.32 | (1 year and 6 months ago) | (in 7 months) | (1 year and 4 months ago) | 4.32.1 (1 year and 4 months ago) |
Liquibase Secure Releases Nearing End of Life - Support Ending Soon (1)
| Release | Released | Technical Support | Fixes | Latest |
|---|---|---|---|---|
| 4.31 | (1 year and 10 months ago) | (in 2 months) | (1 year and 6 months ago) | 4.31.1 (1 year and 9 months ago) |
Liquibase Secure End of Life (EOL) Releases - No Longer Supported (2)
| Release | Released | Technical Support | Fixes | Latest |
|---|---|---|---|---|
| 4.30 | (2 years ago) | (2 weeks and 3 days ago) | (1 year and 10 months ago) | 4.30.0 (2 years ago) |
| 4.29 | (2 years and 3 months ago) | (1 month and 6 days ago) | (2 years ago) | 4.29.3 (2 years and 1 month ago) |
Your Liquibase Secure end of life date depends on one rule: the commercial edition supports every release for 24 months from the day it ships. Below you get the dates for each version, how fixes reach your database tooling, and what to do before support runs out for every database in your estate.
Liquibase Secure End of Life: How Each Release Is Supported
Liquibase supports any release of Liquibase Secure published in the past 2 years. Because the newest release always carries the latest fixes, the policy rewards enterprise teams that keep their database tooling current, unlike open-source projects that publish no schedule.
The Fix-Forward Model and Security Fixes
Liquibase Secure follows a fix-forward model. Bug fixes and security fixes, including a CVE response to newly found vulnerabilities, ship only in the newest release. Older versions are superseded, not patched: they stay supported, yet no patches are backported, so you must upgrade to receive a fix. In short, you fix forward instead of patching backward.
Customer Support, Customer Success and Technical Support
The customer support and customer success teams try to solve your problem without forcing an upgrade whenever possible. Technical support for a release lasts until its own 24-month mark, so open a ticket before that date, not after.
EOL Dates for Each Supported Release
This table shows every supported release, as listed on endoflife.date on 9 October 2026. Releases before 5.0 shipped as Liquibase Pro.
| Release | Fixes | Technical support ends |
|---|---|---|
| 6.0 | Yes | 29 Sep 2028 |
| 5.2 | Ended 29 Sep 2026 | 12 Aug 2028 |
| 5.1 | Ended 9 Jun 2026 | 26 Mar 2028 |
| 5.0 | Ended 18 Feb 2026 | 24 Nov 2027 |
| 4.33 | Ended 30 Sep 2025 | 9 Jul 2027 |
| 4.32 | Ended 9 Jul 2025 | 3 Jul 2027 |
| 4.31 | Ended 21 May 2025 | 17 Feb 2027 |
| 4.30 | Ended 16 Jan 2025 | 5 Nov 2026 |
| 4.29 | Ended 5 Nov 2024 | Ended 16 Oct 2026 |
The newest latest release is 6.0.0, and the table lists each cycle's final build date. Check your own build with liquibase --version; the commercial artifacts ship as Maven packages (liquibase-commercial) and as the Docker image liquibase/liquibase-secure.
Tracking Version Support and the Release Cycle
Each release cycle is supported for 24 months from its own release date, so every new minor version starts a fresh clock. Compare the number your Java build or CI/CD pipelines report with the table, and track version support on endoflife.date rather than relying on memory.
Supported Version Policy for Liquibase Pro, Community and OSS
Liquibase Pro is the old name of today's commercial edition. The Liquibase Community edition, an open source project, also called Liquibase OSS, has no documented life cycle for your database schema tooling: endoflife.date notes that only the latest release is actively maintained, and 4.33.0 (9 Jul 2025) was the last 4.x release. That makes the commercial edition the only one with a written support policy and a dated guarantee.
Liquibase 4.x After the License Change
Liquibase 5 moved to the FSL, a source-available license that later converts to the Apache license 2.0, while 4.x stays Apache 2.0. Projects such as Keycloak need OSI-approved licenses, and the CNCF rejected an exception request. Because 5.x often arrives as a transitive dependency, a framework upgrade can pull in a new major version without anyone noticing the license change. Some teams stay on 4.x or discuss a fork, but with no 4.x releases since July 2025 and no written end-of-life schedule for the open source line, a migration to 5.x or a dated commercial plan is the safer route for security fixes.
Database Change Governance in 6.0 and Your Support Policy
Release 6.0 landed on 29 Sep 2026, so its technical support runs until 29 Sep 2028, and it turns Liquibase Secure into a governance platform for every database change, human or AI agent. Change Intelligence shows database change activity, failures and drift in one place, while centralized governance of policy ships more than 50 prebuilt rules and role-based access control. Governance, drift detection and database change history reach every database only when you run the newest release. Under the support policy you get all of that only by running the newest release.
Upgrade Checklist for the Latest Release
- Run
liquibase --versionin every environment and note the release. - Compare each version with the table and flag anything ending within six months.
- Test the new release against a copy of your database schema and confirm rollback scripts still work.
- Roll the upgrade through your pipelines and record the date for your audit trail of each database change.
Compliance and Audit Evidence After You Upgrade
A supported release keeps your compliance story simple: auditors see policy outcomes and who approved each change, and running a release past its technical support date, such as 4.29 after 16 Oct 2026, means explaining an unpatched version. Treat the end-of-life date as a deadline for that evidence, not just for patches.