Skip to content

Bump org.liquibase:liquibase-core from 4.33.0 to 5.0.2#244

Open
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/maven/org.liquibase-liquibase-core-5.0.2
Open

Bump org.liquibase:liquibase-core from 4.33.0 to 5.0.2#244
dependabot[bot] wants to merge 1 commit intomasterfrom
dependabot/maven/org.liquibase-liquibase-core-5.0.2

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Mar 9, 2026

Bumps org.liquibase:liquibase-core from 4.33.0 to 5.0.2.

Release notes

Sourced from org.liquibase:liquibase-core's releases.

Liquibase v5.0.2

5.0.2 Liquibase Community Release Notes

Liquibase Community v5.0.2 is here, with contributions from developers around the globe. This release includes a range of bug fixes across multiple database platforms along with several quality-of-life enhancements, with 19 contributors coming together to continue improving Liquibase for the entire community.

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. Learn more on our GitHub README

  • Quarterly Community Releases – Liquibase Community updates are released on a quarterly cadence (every second month of each calendar quarter) 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.

A huge thank you to every contributor who filed an issue, submitted a pull request, or helped review code. You are the engine that drives Liquibase forward.


What’s in this release

Notable improvements

(#7451) by @​MalloD12 New: Added the ALLOW_INHERIT_LOGICAL_FILE_PATH global configuration property, which controls whether included changelogs inherit the logicalFilePath of their parent changelog when no explicit logicalFilePath is set.

(#6627 and #7390) by @​mkarg Improved: Custom change classes that cannot be found on the classpath no longer automatically fail the entire changelog. Liquibase now honors failOnError: false at the changeset level when the failure is caused by a missing custom change class. Additionally, a failing precondition with onFail="MARK_RAN" is now respected when the custom change class is not on the classpath.

(#7479) Improved Cassandra compatibility: Refactoring to enable third-party extensions like liquibase-cassandra to provide database-specific implementations and laying the groundwork for a future fix for CQL incompatibility errors.

Liquibase Community 5.0.2 moves more community repositories to the Functional Source License (FSL). See our FSL blog for details.

Performance improvements

(#7439) Performance fix for analytics: @​tati-qalified identified and resolved a performance degradation introduced with the analytics implementation. If you noticed Liquibase running slower since analytics was added, this is the fix you've been waiting for.

(#7539) Build improvements: Groovy source compilation has been moved to the module level in liquibase-extension-testing, removing redundant build steps from the root configuration.

Drivers and Dependencies

(7528) Updated bundled JDBC driver versions: MSSQL to v13.2.1.jre11 and Firebird to v6.0.3

(#7469) Dependency cleanup: Explicit exclusions added to liquibase-core pom.xml to fix duplicated commons-text dependency.

Fixes

(#7489) by @​MalloD12 Resolved an issue where the maven-update command logged duplicate messages when using the Java API. Summary output now defaults to LOG instead of ALL, which previously caused messages to be written to both the console and the log simultaneously. This behavior can still be overridden by explicitly setting the showSummaryOutput argument.

(#7395) by @​Parthiee Invalid or empty changelog file paths are now caught and rejected during serialization

Liquibase now validates that changelog file paths are properly defined and non-empty when serializing changelog configurations. Previously, incomplete or missing paths could pass through silently, resulting in invalid configurations.

... (truncated)

Changelog

Sourced from org.liquibase:liquibase-core's changelog.

Liquibase Community 5.0.2 is a minor patch release

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

Changes

Notable Changes

New Features

Bug Fixes

... (truncated)

Commits
  • 2c889ad Update changelog.txt for 5.0.2 (#7583)
  • bbb74fb Skip bot PRs in Claude Code review workflow (#7581)
  • c6eaa32 chore(deps-dev): bump com.oracle.database.jdbc:ojdbc8 from 19.29.0.0 to 19.30...
  • 49ec08e chore(deps): bump the production-deps group with 6 updates (#7568)
  • a65eeb4 chore(deps): bump spring.version from 7.0.3 to 7.0.5 (#7567)
  • fb9f288 chore(deps-dev): bump net.snowflake:snowflake-jdbc from 3.28.0 to 4.0.0 (#7541)
  • c4c907e chore(deps-dev): bump org.javacc.plugin:javacc-maven-plugin from 3.0.3 to 3.8...
  • 7f61ae5 chore(deps): bump the test-deps group with 4 updates (#7561)
  • 00ef199 chore(deps): bump junit-jupiter.version from 6.0.2 to 6.0.3 (#7562)
  • 8784316 chore(deps): bump the github-actions group across 1 directory with 4 updates ...
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [org.liquibase:liquibase-core](https://github.com/liquibase/liquibase) from 4.33.0 to 5.0.2.
- [Release notes](https://github.com/liquibase/liquibase/releases)
- [Changelog](https://github.com/liquibase/liquibase/blob/master/changelog.txt)
- [Commits](liquibase/liquibase@v4.33.0...v5.0.2)

---
updated-dependencies:
- dependency-name: org.liquibase:liquibase-core
  dependency-version: 5.0.2
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java Pull requests that update Java code labels Mar 9, 2026
@dependabot dependabot bot requested review from takezoe and xuwei-k as code owners March 9, 2026 12:50
@dependabot dependabot bot added the java Pull requests that update Java code label Mar 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file java Pull requests that update Java code

Development

Successfully merging this pull request may close these issues.

0 participants