Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@renovate-bot
Copy link
Contributor

@renovate-bot renovate-bot commented Nov 10, 2025

This PR contains the following updates:

Package Change Age Confidence
org.liquibase:liquibase-core (source) 4.31.1 -> 5.0.1 age confidence

Release Notes

liquibase/liquibase (org.liquibase:liquibase-core)

v5.0.1

See the Liquibase Community 5.0.1 Release Notes for the complete set of release information.

License corrections for Maven

The license block for Maven users has been corrected to use the Functional Source License (FSL).

Changelog

-(#​7350) Update licensing and documentation for Community distribution by @​filipelautert

Changes in version 5.0.0 (2025.09.30)

v5.0.0: Liquibase v5.0.0

Liquibase Community 5.0 is a major release

See the Liquibase Community 5.0 Release Notes for the complete set of release information.

⚠️ MAJOR CHANGES IN COMMUNITY AND COMMERCIAL DISTRIBUTIONS

Liquibase is evolving to better serve both open-source contributors and enterprise customers by introducing a clearer separation between its open source Community and the commercial Secure offering. This change is designed to ensure that each distribution is optimized for its respective users: providing open-source Community users with flexibility and control, while delivering scalability, reliability, and governance for Secure enterprise teams. The changes provide Liquibase Secure customers:

  • Developer Productivity. Enable developers with autonomy and guardrails built directly into their daily workflow.
  • Secure Automation. Embed governance, security, and compliance into every change automatically.
  • Change Insights. Deliver audit-ready visibility so every change is trusted, explainable, and observable.

The new structure enables Liquibase to more effectively support developers at all stages—from experimentation and community collaboration to mission-critical deployments. Therefore, starting with this Liquibase 5.0 release, only the open source Community distribution is available at the traditional Github, Docker, and Maven access channels.

If you need the Secure commercial offering, please visit Liquibase.com

Liquibase Community Licensing Change

Additionally, Liquibase Community is now licensed under the Functional Source License (FSL). See LICENSE file at the root of the distribution for details. Starting with Liquibase 5.0, contributors will be asked to sign a one-time Contributor License Agreement (CLA). This is handled automatically by CLA Assistant when you open your first pull request.

Liquibase 5.0 Community Release Notable Changes

Liquibase Package Manager (LPM) integrated to enable users to install, update, and manage their dependencies
  • The open source Liquibase Community 5.0 ships without extensions, drivers, and many other packages and dependencies. This change provides a much lighter, modular, and customizable Liquibase experience for Community users. Importantly, this flexibility both allows and requires users to manage their Liquibase dependencies for their specific needs.
  • Liquibase Package Manager is now integrated and available for use directly from within the Community CLI experience with a new liquibase lpm command as the preferred method for managing dependencies.
  • Learn more at the LPM README
Liquibase Community 5.0+ ships with the Functional Source License (FSL)
  • "The Functional Source License (FSL) is a Fair Source license that converts to Apache 2.0 or MIT after two years. It is designed for SaaS companies that value both user freedom and developer sustainability. FSL provides everything a developer needs to use and learn from your software without harmful free-riding."
  • Learn more at https://fsl.software/
SnowFlake JDBC Driver CVE Fix
  • Liquibase 5.0 patches a vulnerability found in Snowflake JDBC driver (CVE-2025-24789) and resolves issue with logicalfilepath reported in 4.31.0. Note: Neither open source Community nor the commercial Secure products were affected by this CVE.
Dropped support for Java 8 and Java 11
  • The minimal Java dependency for Liquibase 5.0+ is Java 17. This update enables Liquiabase to build, test, and ship with modern and more secure dependencies.
ValueDate Checksum bug fix
  • In the last release, an issue was introduced by a change in how valueDate was calculated and incorporated into the checksum calculations. This issue has been fixed by ensuring that rawDatevalue is excluded from checksum calculations.
  • (#​7101) fix: prevent rawDateValue from being used for checksum calculations @​filipelautert

Changelog of Community PRs

🚀 New Features

🐛 Bug Fixes 🛠

DevOps

🤖 Security, Driver and Other Updates

44 changes - (#​7301) chore(deps): bump org.apache.commons:commons-lang3 from 3.18.0 to 3.19.0 in the production-deps group by dependabot - (#​7302) chore(deps-dev): bump the build-tools group with 2 updates by dependabot bot - (#​7297) chore(deps-dev): bump the production-deps group with 2 updates by dependabot bot - (#​7294) chore(deps-dev): bump org.assertj:assertj-core from 3.27.5 to 3.27.6 in the test-deps group by dependabot bot - (#​7291) chore(deps): bump the build-tools group with 3 updates by dependabot bot - (#​7292) Remove update-docs-oss-pro-version job @​sayaliM0412 - (#​7291) chore(deps): bump the build-tools group with 3 updates @​dependabot[bot] - (#​7284) chore(deps-dev): bump org.postgresql:postgresql from 42.7.7 to 42.7.8 in the build-tools group @​dependabot[bot] - (#​7283) chore(deps-dev): bump org.assertj:assertj-core from 3.27.4 to 3.27.5 in the test-deps group @​dependabot[bot] - (#​7281) chore(deps): bump org.projectlombok:lombok from 1.18.40 to 1.18.42 @​dependabot[bot] - (#​7277) chore(deps): bump the build-tools group with 3 updates @​dependabot[bot] - (#​7266) chore(deps-dev): bump org.mariadb.jdbc:mariadb-java-client from 3.5.5 to 3.5.6 in the build-tools group @​dependabot[bot] - (#​7251) chore(deps): bump org.projectlombok:lombok from 1.18.38 to 1.18.40 @​dependabot[bot] - (#​7252) chore(deps): bump actions/github-script from 7 to 8 in the github-actions group @​dependabot[bot] - (#​7242) chore(deps): bump the github-actions group across 1 directory with 3 updates @​dependabot[bot] - (#​7241) chore(deps-dev): bump the build-tools group across 1 directory with 2 updates @​dependabot[bot] - (#​7236) chore(deps): bump org.yaml:snakeyaml from 2.4 to 2.5 @​dependabot[bot] - (#​7234) chore(deps): bump org.sonarsource.scanner.maven:sonar-maven-plugin from 5.1.0.4751 to 5.2.0.4988 in the build-tools group @​dependabot[bot] - (#​7223) chore(deps-dev): bump org.firebirdsql.jdbc:jaybird from 5.0.8.java8 to 5.0.9.java8 in the build-tools group @​dependabot[bot] - (#​7225) chore(deps): bump actions/setup-java from 4 to 5 in the github-actions group @​dependabot[bot] - (#​7207) chore(deps): bump org.apache.maven.plugins:maven-javadoc-plugin from 3.11.2 to 3.11.3 in the build-tools group @​dependabot[bot] - (#​7206) chore(deps): bump actions/checkout from 4 to 5 in the github-actions group @​dependabot[bot] - (#​7203) chore(deps): bump org.mockito:mockito-core from 4.11.0 to 5.19.0 @​dependabot[bot] - (#​7198) chore(deps-dev): bump net.snowflake:snowflake-jdbc from 3.25.1 to 3.26.0 in the build-tools group @​dependabot[bot] - (#​7195) chore(deps): bump org.firebirdsql:firebird-testcontainers-java from 1.5.1 to 1.6.0 @​dependabot[bot] - (#​7189) chore(deps): bump the github-actions group with 2 updates @​dependabot[bot] - (#​7188) chore(deps-dev): bump org.mariadb.jdbc:mariadb-java-client from 3.5.4 to 3.5.5 in the build-tools group @​dependabot[bot] - (#​7185) chore(deps-dev): bump org.assertj:assertj-core from 3.27.3 to 3.27.4 in the test-deps group @​dependabot[bot] - (#​7160) chore(deps-dev): bump org.apache.commons:commons-compress from 1.27.1 to 1.28.0 in the production-deps group @​dependabot[bot] - (#​7164) chore(deps-dev): bump the build-tools group across 1 directory with 2 updates @​dependabot[bot] - (#​7157) chore(deps): bump com.opencsv:opencsv from 5.10 to 5.12.0 @​dependabot[bot] - (#​7135) chore(deps): bump commons-io:commons-io from 2.19.0 to 2.20.0 @​dependabot[bot] - (#​7156) chore(deps): bump org.codehaus.mojo:flatten-maven-plugin from 1.7.1 to 1.7.2 in the build-tools group @​dependabot[bot] - (#​7132) chore(deps): bump the github-actions group with 2 updates @​dependabot[bot] - (#​7150) chore(deps): bump org.apache.commons:commons-text from 1.13.1 to 1.14.0 in the production-deps group @​dependabot[bot] - (#​7139) chore(deps-dev): bump the build-tools group across 1 directory with 2 updates @​dependabot[bot] - (#​7142) chore(deps): bump the test-deps group across 1 directory with 7 updates @​dependabot[bot] - (#​7127) chore(deps): bump the build-tools group across 1 directory with 3 updates @​dependabot[bot] - (#​7115) chore(deps): bump the test-deps group with 5 updates @​dependabot[bot] - (#​7120) chore(deps): bump the production-deps group with 2 updates @​dependabot[bot] - (#​7121) chore(deps): bump targetMavenVersion from 3.9.10 to 3.9.11 @​dependabot[bot] - (#​7119) Fix dependabot.yml version syntax error @​jnewton03 - (#​7117) Add Spring Framework 6.x to dependabot ignore list @​jnewton03 - (#​7106) Reduce dependabot PR overload through strategic grouping and automation @​jnewton03
Full Changelog: https://github.com/liquibase/liquibase/compare/v4.33.0...v5.0.0
Get Certified

Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.

Read the Documentation

Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.

Join the Community

Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:
Contribute code
Make doc updates
Help by asking and answering questions
Join our Discord server
Sign up to provide feedback to the product team
Thanks to everyone who helps make Liquibase better!

File Descriptions

Liquibase CLI -- Includes open source + commercial functionality

  • liquibase-x.y.z.tar.gz -- Archive in tar.gz format
  • liquibase-x.y.z.zip -- Archive in zip format
  • liquibase-windows-x64-installer-x.y.z.exe -- Installer for Windows
    Primary Libraries - For embedding in other software
  • liquibase-core-x.y.z.jar – Base Liquibase library (open source)
  • liquibase-commerical-x.y.z.jar – Additional commercial functionality
  • liquibase-additional-x.y.z.zip – Contains additional, less commonly used files
  • Additional libraries such as liquibase-maven-plugin.jar and liquibase-cdi.jar
  • Javadocs for all the libraries
  • Source archives for all the open source libraries
  • ASC/MD5/SHA1 verification hashes for all files

v4.33.0

Compare Source

Liquibase 4.33.0 delivers important updates across Policy Checks, Change Automation, and other areas of platform enhancement, along with critical bug fixes and improvements to MongoDB, PostgreSQL, and DB2 on Z/OS support.
See the Liquibase 4.33.0 Release Notes for the complete set of release information.

Notable Changes

[PRO]

Change Automation
  • PostgreSQL Composite TYPE Support in Database Inspection. Liquibase Pro now includes support for inspecting PostgreSQL Composite TYPE objects during database inspection operations such as snapshot and diff. This enhancement ensures Composite TYPEs appear in inspection outputs, helping users manage and track changes to complex data structures more effectively. [INT-1249] [INT-135]
  • PostgreSQL Composite TYPE Support in generate-changelog and diff-changelog. Liquibase Pro now includes support for detecting PostgreSQL composite TYPE objects during generate-changelog and diff-changelog operations. This enhancement ensures that composite TYPE definitions—used to group multiple fields into a custom data structure—are captured and modeled alongside other schema elements, helping users manage and track changes more comprehensively. [INT-1251]
  • PostgreSQL Password Escaping Enhancement. Liquibase now escapes special characters in PostgreSQL passwords when using the psql native executor. Previously, if a password included characters requiring percent-encoding (such as @​, %, or #), the executor would fail with a psql: error: invalid percent-encoded token message. [DAT-20254]
  • Db2 on Z/OS JCL Executor. Liquibase Pro now includes the ability to submit JCL jobs to the mainframe via Db2 DSNUTILU stored procedure. This enables users to automate more sophisticated procedures by integrating system level activities and database activities in a standard changelog format. This feature is enabled by a runwith:JCL decoration on applicable changesets containing properly formatted JCL.[INT-573, INT-1217]
  • Improved Persistent Spool File Behavior for SQLPlus Executor. The SQLPlus executor ensures that spool files are always retained when --sqlplus-create-spool=true, giving users consistent access to output files. Previously, spool file retention was tied to the --sqlplus-keep-temp setting; now, this setting applies only to temporary SQL files, not spool files. This decoupling improves clarity and gives users more control—if a spool file is created, it will remain unless users opt out by setting --sqlplus-create-spool=false. [DAT-18983]
Policy Checks
  • MongoChangetypeAttributes Policy Check. Introduced a new quality check named MongoChangetypeAttributes that allows users to enforce specific values or patterns for attributes within MongoDB-specific changetypes. Users can select a single Mongo changetype (e.g., createIndex, dropCollection) and specify expected values or patterns for its attributes. The check triggers if a specified attribute is present but does not match the defined value or regex—ensuring consistent standards across Mongo changesets. This supports validation across key changetypes attributes like adminCommand, createCollection, insertOne, and more, and enhances control and quality enforcement in MongoDB deployment pipelines. [DAT-18275]

[Community]

Important dependency updates
  • Liquibase Community 4.33+ has Java 24 core build support.
  • The liquibase-cdi and liquibase-cdi-jakarta modules are still supported, but have been removed from the Community distribution to their own repositories.

️[PRO] and [Community] Upcoming Change in Distributions

Liquibase is evolving to better serve both open-source contributors and enterprise customers by introducing a clearer separation between its Community and PRO offerings. This change is designed to ensure that each distribution is optimized for its respective users—providing Community users with flexibility and control, while delivering scalability, reliability, and governance for enterprise teams.
The new structure enables Liquibase to more effectively support developers at all stages—from experimentation and community collaboration to mission-critical deployments. Liquibase 4.32.0 introduced the first general availability (GA) release of independently packaged Pro distributions, along with dedicated distribution channels and key-based access enforcement for Pro capabilities. This marks a significant step toward delivering a curated, enterprise-grade experience for Pro users.
The Community distribution and its delivery channels remain unchanged in this phase.

PRO PRs

New Features
Bug Fixes

Version updates: In the pom.xml for Maven, update postgres to 42.7.7 liquibase/liquibase-pro#2486 by @​abrackx

Security, Driver and Other Updates

Community PRs

New Features
Bug Fixes
Security, Driver and Other Updates
Full Changelog: liquibase/liquibase@v4.32.0...v4.33.0

Changes in version 4.32.0 (2025.05.21)

Liquibase 4.32.0 is a major release

See the Liquibase 4.32.0 Release Notes for the complete set of release information.

[PRO] and [Community] Upcoming Change in Distributions

Liquibase is evolving to better serve both open-source contributors and enterprise customers by introducing a clearer separation between its Community and PRO offerings. This change is designed to ensure that each distribution is optimized for its respective users—providing Community users with flexibility and control, while delivering scalability, reliability, and governance for enterprise teams. The new structure enables Liquibase to more effectively support developers at all stages—from experimentation and community collaboration to mission-critical deployments.
Liquibase 4.32.0 introduces the first general availability (GA) release of independently packaged Pro distributions, along with dedicated distribution channels and key-based access enforcement for Pro capabilities. This marks a significant step toward delivering a curated, enterprise-grade experience for Pro users.
The Community distribution and its delivery channels remain unchanged in this phase.

Notable Changes

[PRO]
Example PRO notable change

Policy Checks
Formatted SQL Header Policy Check. Introduced a new policy check named FormattedSqlHeaderRequired to ensure that.sql files included in changelogs begin with the required --liquibase formatted sql header. This check helps prevent improperly formatted SQL changes that could bypass Liquibase’s change tracking, auditing, and rollback features. This new policy check supports changelogs of any format (SQL, XML, YAML, JSON) and includes an EXCEPTIONS_LIST customization option to exclude specific files. When triggered, it lists all offending .sql files missing the required header, helping maintain the integrity and reliability of database change management. [DAT-19042]
Get Config Value Helper Function for Python Checks. Added a new helper function, liquibase_utilities.get_config_value(), for custom Python checks. This function enables easy access to standard Liquibase configuration properties—including those set via environment variables, CLI arguments, or defaults files. This enhancement simplifies scripting by allowing users to retrieve values such as url, loglevel, changelogfile, and custom properties like dbplatform or contexts directly within their Python checks, without manually resolving property names or sources. [DAT-19486]
Property Substitution in Python Check Script Arguments. Enhanced support for custom Python checks by allowing the use of Liquibase properties in the SCRIPT_ARGS section. Users can now reference properties—such as environment variables, CLI arguments, or values from the defaults file—using standard substitution syntax (e.g., ${liquibase.command.url} or ${PIPELINE_NAME}). This enables dynamic and context-aware scripting, such as configuring behavior based on ru


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@forking-renovate forking-renovate bot added the renovate https://renovate.whitesourcesoftware.com [FINERACT-962] label Nov 10, 2025
@renovate-bot renovate-bot force-pushed the renovate/org.liquibase-liquibase-core-5.x branch from 5a57caa to 839dbc4 Compare November 10, 2025 20:40
@galovics galovics merged commit 4e71edd into apache:develop Nov 11, 2025
34 checks passed
@renovate-bot renovate-bot deleted the renovate/org.liquibase-liquibase-core-5.x branch November 11, 2025 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

renovate https://renovate.whitesourcesoftware.com [FINERACT-962]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants