Liquibase End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 5.0.4

Liquibase end of life (EOL) and end of support (EOS) dates: 33 Liquibase versions have reached EOL, including Liquibase 4.31 (EOL date: May 21, 2025) — no longer receiving security updates or patches. Liquibase 5.0.4 is the current supported release — 2 versions in active support. Also see Jenkins end of support dates for related end-of-life information.

Liquibase end of life dates timeline — release schedule chart of the 8 most recent Liquibase versions, mapping security support windows against their EOL dates
Liquibase end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Liquibase releases of 35 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Liquibase EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Liquibase Releases - Active EOS/EOSL Support (2)

Release Released Security Support Latest
5 (1 year and 1 month ago) Active 5.0.4 (3 months ago)
4.32 (1 year and 6 months ago) Active 4.32.0 (1 year and 6 months ago)

Liquibase End of Life (EOL) Releases - No Longer Supported (33)

Release Released Security Support Latest
4.31 (1 year and 10 months ago) (1 year and 6 months ago) 4.31.1 (1 year and 9 months ago)
4.30 (2 years ago) (1 year and 10 months ago) 4.30.0 (1 year and 10 months ago)
4.29 (2 years and 3 months ago) (1 year and 10 months ago) 4.29.2 (2 years and 2 months ago)
4.28 (2 years and 6 months ago) (2 years and 3 months ago) 4.28.0 (2 years and 6 months ago)
4.27 (2 years and 7 months ago) (2 years and 6 months ago) 4.27.0 (2 years and 7 months ago)
4.26 (2 years and 9 months ago) (2 years and 7 months ago) 4.26.0 (2 years and 9 months ago)
4.25 (3 years ago) (2 years and 9 months ago) 4.25.1 (2 years and 11 months ago)
4.24 (3 years and 1 month ago) (3 years ago) 4.24.0 (3 years and 1 month ago)
4.23 (3 years and 4 months ago) (3 years and 1 month ago) 4.23.2 (3 years and 2 months ago)
4.22 (3 years and 6 months ago) (3 years and 4 months ago) 4.22.0 (3 years and 6 months ago)
4.21 (3 years and 7 months ago) (3 years and 6 months ago) 4.21.1 (3 years and 7 months ago)
4.20 (3 years and 8 months ago) (3 years and 7 months ago) 4.20.0 (3 years and 8 months ago)
4.19 (3 years and 10 months ago) (3 years and 8 months ago) 4.19.1 (3 years and 8 months ago)
4.18 (3 years and 11 months ago) (3 years and 10 months ago) 4.18.0 (3 years and 11 months ago)
4.17 (4 years and 1 month ago) (3 years and 11 months ago) 4.17.2 (4 years ago)
4.16 (4 years and 2 months ago) (4 years and 1 month ago) 4.16.1 (4 years and 2 months ago)
4.15 (4 years and 3 months ago) (4 years and 2 months ago) 4.15.0 (4 years and 3 months ago)
4.14 (4 years and 3 months ago) (4 years and 3 months ago) 4.14.0 (4 years and 3 months ago)
4.13 (4 years and 4 months ago) (4 years and 3 months ago) 4.13.0 (4 years and 4 months ago)
4.12 (4 years and 5 months ago) (4 years and 4 months ago) 4.12.0 (4 years and 5 months ago)
4.11 (4 years and 5 months ago) (4 years and 5 months ago) 4.11.0 (4 years and 5 months ago)
4.10 (4 years and 6 months ago) (4 years and 5 months ago) 4.10.0 (4 years and 6 months ago)
4.9 (4 years and 8 months ago) (4 years and 6 months ago) 4.9.1 (4 years and 7 months ago)
4.8 (4 years and 9 months ago) (4 years and 8 months ago) 4.8.0 (4 years and 9 months ago)
4.7 (4 years and 10 months ago) (4 years and 9 months ago) 4.7.1 (4 years and 10 months ago)
4.6 (5 years ago) (4 years and 10 months ago) 4.6.2 (4 years and 11 months ago)
4.5 (5 years and 1 month ago) (5 years ago) 4.5.0 (5 years and 1 month ago)
4.4 (5 years and 5 months ago) (5 years and 1 month ago) 4.4.3 (5 years and 3 months ago)
4.3 (5 years and 9 months ago) (5 years and 5 months ago) 4.3.5 (5 years and 6 months ago)
4.2 (6 years ago) (5 years and 9 months ago) 4.2.2 (5 years and 11 months ago)
4.1 (6 years and 1 month ago) (6 years ago) 4.1.1 (6 years and 1 month ago)
4 (6 years and 4 months ago) (1 year and 1 month ago) 4.33.0 (1 year and 4 months ago)
4.0 (6 years and 4 months ago) (6 years and 1 month ago) 4.0.0 (6 years and 4 months ago)

Your Liquibase end of life date depends on the edition you run, because the open-source and commercial lines follow different rules. Liquibase applies database schema changes through changelogs, and as of October 2026 the open-source Liquibase 4.x line is no longer maintained, while 5.x receives every fix. This guide shows what each build gets and how to plan your move.

Liquibase End of Life Status for OSS Releases

For open-source users, only the newest build gets attention. The tracker endoflife.date notes that the project follows loose semantic versioning, so breaking changes can land in minor releases, and that only the newest build is actively maintained. Check what you run with liquibase --version.

Liquibase 4.x Support Policy After 4.33

The 4.x branch has no published support policy. Its final build, 4.33.0, shipped on 9 July 2025, and security support for 4.x ended on 30 September 2025. No patch releases, bug fixes or security fixes have followed, so a CVE in a bundled library stays open unless you override it. Treat vulnerabilities on 4.x as your own problem.

Liquibase 5.0 Release Cycle and Latest Release

Release 5.0 arrived on 30 September 2025, and 5.0.4 followed on 20 August 2026. With no stated release cycle, move to each new latest release to keep receiving fixes.

Liquibase Secure Supported Version Policy for the Commercial Edition

Liquibase Secure, formerly Liquibase Pro, is the commercial edition. Each cycle gets technical support for 24 months, and the supported release dates below come from endoflife.date. Older Enterprise installs can ask the vendor's support desk for their own dates.

ReleasePublishedTechnical support ends
6.029 Sep 202629 Sep 2028
5.29 Jun 202612 Aug 2028
5.118 Feb 202626 Mar 2028
5.030 Sep 202524 Nov 2027
4.339 Jul 20259 Jul 2027
4.305 Nov 20245 Nov 2026
4.2925 Jul 2024Ended 16 Oct 2026

How the Fix Forward Model Works

Under a fix forward model, nothing is back-ported: bug fixes and security patches ship in the newest build only. Older builds remain supported for their 24 months, but you must upgrade to receive a fix.

Tracking Supported Release Dates

Instead of rechecking the table, subscribe to the RSS feed or the iCalendar feed, which publish each cycle's dates, or read the JSON API.

Liquibase OSS License Change: Apache 2.0 Versus FSL

The 5 line moved the core from the Apache license to the Functional Source License (FSL), which converts back to Apache 2.0 after two years. That license change hit the community hardest: the 4.x community edition kept its open terms but gets no maintenance, so teams that need open source terms for compliance are stuck on unpatched code or on a fork. Because Liquibase is a Java library, the issue reaches every dependency tree that embeds it.

Why Keycloak and CNCF Projects Care

Keycloak belongs to the CNCF, which expects OSI-approved terms for every dependency. The foundation rejected an exception request, which pushed the wider ecosystem to ask Liquibase for a fix.

Spring Boot and Transitive Dependency Risk

The newest Spring Boot already pulls in 5.x, so many teams absorb the change as a transitive dependency without noticing. One commenter argued it belonged under a new Maven groupId. Audit your build tree.

Liquibase 5.0 Modular Packaging and Extensions

Beyond licensing, 5.0 made the distribution modular. Extensions and drivers are no longer bundled and come from the Liquibase package manager. Projects using Maven, Gradle, Ant or Spring Boot are mostly unaffected, but CLI and Docker users, and anyone installing RPM, DEB or Homebrew packages, must supply their own database driver. Existing changelogs keep working.

Planning a Liquibase Pro Upgrade Path Before Support Ends

Choose your path by edition, then act before your build stops getting fixes.

Steps for Liquibase OSS Users

  1. Confirm your current version; anything on 4.x gets no fixes.
  2. Read the readiness checklist, then test 5.x in CI.
  3. Migrate drivers and extensions you relied on, and plan the migration in one change window.

Steps for Liquibase Secure Customers

Stay on a cycle inside its 24-month window and schedule the move before your date. If you want an SLA-backed, predictable track, this commercial route is the one built for it.

EOL dates of related software products