Bump org.liquibase:liquibase-core from 4.25.0 to 4.25.1

[dependabot]

Bumps org.liquibase:liquibase-core from 4.25.0 to 4.25.1.

Release notes

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

Liquibase v4.25.1

Liquibase 4.25.1 is a patch release

[!NOTE] See the Liquibase 4.25.1 Release Notes for the complete set of release information.

Notable Changes

[PRO]

Observability: Update Reports

• These reports give you insights into the status of your database and enable you to quickly find and resolve errors in your automation pipeline. These reports can also help you detect patterns of failures that you can catch with Quality Checks or use to inform internal training and education for your teams.
• Learn more about Update Reports

Observability: Drift Report extended to diffchangelog command

• With our new HTML format, you can quickly see the differences between databases, including detailed object differences. This easy-to-read and shareable report makes it faster than ever to detect and fix database drift.
• Learn more Drift Reports

Observability: Structured Logging Enhancement

Thanks to your feedback, we’ve added a new set of keys that improves data analysis capabilities surrounding exceptions and Quality Checks. Learn more at Structured Logging

Convenience: new liquibase connect command

• A new command to test your database's url, username, and password are all configured correctly and that Liquibase can reach your database -- and no changelog required.
• Learn more liquibase connect command

Convenience: Global endDelimiters

• Global endDelimiters decrease the friction of incorporating work from different teams and save you time from the manual process of updating existing code.
• Learn more Global endDelimiters

[PRO]

Changes and Bug Fixes

• (#1417) DAT-16405: make report arguments visible on update-family commands by StevenMassaro
• (#1361) DAT-16064: Added test for exception details by wwillard7800
• (#1420) DAT-16429: Handle no license key in checks run command by wwillard7800
• (#1411) DAT-16063: include changeset identifier in log message for failing comment removal by StevenMassaro
• (#1408) DAT-15379: Updated pattern matching for 'USE DATABASE' statements by filipelautert
• (#1404) DAT-16157: do not upgrade checks file if autoUpdate is off by StevenMassaro
• (#1390) DAT-14570: add checks run results to MDC by StevenMassaro
• (#1401) DAT-16322: add liquibase connect command by StevenMassaro
• (#1398) DAT-16318: Handle rollback changes during modifyChangeSets logic by wwillard7800
• (#1389) DAT-16207: Styled update reports by abrackx
• (#1383) DAT-16136: expand TableMustHaveAComment check to check changelogs by StevenMassaro
• (#1366) DAT-15394: Generate report for diff-changelog by abrackx
• (#1387) Init checksSettingsFiles list to avoid NPE by wwillard7800
• (#1364) DAT-15404: Tweak endDelimiter name and remove hidden flag by wwillard7800

... (truncated)

Changelog

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

Liquibase 4.25.1 is a patch release

Notable Changes

[PRO]

Observability: Update Reports

• These reports give you insights into the status of your database and enable you to quickly find and resolve errors in your automation pipeline. These reports can also help you detect patterns of failures that you can catch with Quality Checks or use to inform internal training and education for your teams.
• Learn more about Update Reports

Observability: Drift Report extended to diffchangelog command

• With our new HTML format, you can quickly see the differences between databases, including detailed object differences. This easy-to-read and shareable report makes it faster than ever to detect and fix database drift.
• Learn more Drift Reports

Convenience: new liquibase connect command

• A new command to test your database's url, username, and password are all configured correctly and that Liquibase can reach your database -- and no changelog required.
• Learn more liquibase connect command

Convenience: Global endDelimiters

• Global endDelimiters decrease the friction of incorporating work from different teams and save you time from the manual process of updating existing code.
• Learn more Global endDelimiters

[PRO]

Changes and Bug Fixes

• (#1417) DAT-16405: make report arguments visible on update-family commands by StevenMassaro
• (#1361) DAT-16064: Added test for exception details by wwillard7800
• (#1420) DAT-16429: Handle no license key in checks run command by wwillard7800
• (#1411) DAT-16063: include changeset identifier in log message for failing comment removal by StevenMassaro
• (#1408) DAT-15379: Updated pattern matching for 'USE DATABASE' statements by filipelautert
• (#1404) DAT-16157: do not upgrade checks file if autoUpdate is off by StevenMassaro
• (#1390) DAT-14570: add checks run results to MDC by StevenMassaro
• (#1401) DAT-16322: add liquibase connect command by StevenMassaro
• (#1398) DAT-16318: Handle rollback changes during modifyChangeSets logic by wwillard7800
• (#1389) DAT-16207: Styled update reports by abrackx
• (#1383) DAT-16136: expand TableMustHaveAComment check to check changelogs by StevenMassaro
• (#1366) DAT-15394: Generate report for diff-changelog by abrackx
• (#1387) Init checksSettingsFiles list to avoid NPE by wwillard7800
• (#1364) DAT-15404: Tweak endDelimiter name and remove hidden flag by wwillard7800
• (#1351) DAT-15640: Report for updateToTag by wwillard7800
• (#5366) add duplicatedChangesets to MDC (DAT-16452) @​StevenMassaro
• (#1400) DAT-16268: Fix unexpected objects verbiage by abrackx
• (#1342) Fixes problematic V8 checksums for pro CreateFunctionChange by filipelautert

[OSS]

New Features

• (#5186) Adding exception details key and implementation DAT-16064 @​wwillard7800
• (#5323) Updated PrimaryKeyExistsPrecondition to require table name for H2 databases @​filipelautert
• (#5268) Rework update summary to support reporting, add new update report fields (DAT-16207) @​abrackx
• (#5130) Update MySQL boolean behaviour from TinyInt(1) to TinyInt @​MalloD12

... (truncated)

Commits

• d208bf9 Release notes 4.25.1 (#5399)
• 73cb2e1 DAT-16494 Revert "Implemented ability for formatted SQL changelog to have rol...
• e605cee Update create-release.yml: set draft to true (#5388)
• 13df781 fix: use full commit-sha (#5387)
• 196a97c DAT-16471 DevOps: Attach artifatcs job fail (#5370)
• 15bf699 Downgrade ubuntu tests version (#5386)
• 87cf995 Downgrade ubuntu runner images version as current one are failing (#5384)
• 4136260 use first 7 digits of commit-sha (#5379)
• 8fb86c7 DAT-13175 Full automation of OSS extension release (#5383)
• 1408747 Merge pull request #5305 from liquibase/DAT-16354
• Additional commits viewable in compare view

You can trigger a rebase of this PR 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)

[quarkus-bot]

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.