Skip to content

build(deps): bump liquibase.version from 4.24.0 to 4.31.0 in /backend #1014

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
dependabot wants to merge 1 commit into from
Closed

build(deps): bump liquibase.version from 4.24.0 to 4.31.0 in /backend #1014

dependabot wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 11, 2025

Bumps liquibase.version from 4.24.0 to 4.31.0.
Updates org.liquibase:liquibase-core from 4.24.0 to 4.31.0

Release notes

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

Liquibase v4.31.0

Liquibase 4.31.0 is a major release

[!IMPORTANT] Liquibase 4.31.0 contains an expanded Checks Extension, and so the artifact size has increased.

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

⚠️ Breaking Change

Changesets with entirely blank IDs will now fail validation. This change improves the reliability and diagnosability of database changes, and enforces the best-practices set forth in documentation and training.

This validation does not apply to changesets that have already been deployed. However, any changesets marked as runOnChange or runAlways will fail validation if they have an empty changeset ID.

UPDATE: Reported Problems with LogicalFilePath

A few OSS users have reported a logicalfilepath bug, described below. This update aims to highlight potential trouble for users who meet three specific conditions:

  1. Use Liquibase 4.31.0
  2. Use the logicalfilepath attribute with different values at changelog and changeset levels
  3. Use include/includeAll to nest changelogs

The Bug The standard Liquibase practice is to accept the attribute closest to the changeset. But in 4.31.0, the parent logicalfilepath value will be used in DBCL/DBCLH as the changelogfilepath value.

What Next? If your workflow meets the conditions mentioned above, please avoid upgrading to version 4.31.0. The issue will be resolved in the upcoming 4.31.1 release.

Notable Changes

[PRO]

New Checks extension delivered in the box

  • Policy Checks are undoubtedly one of Liquibase Pro's stickiest capabilities, for which we continually add database platforms, new checks, and customizations. But to get these developments, users would need to download and upgrade to the latest Liquibase. Not any more! With this new checks extension, you can deploy the latest Policy Checks powers by optionally upgrading just the Check Extension on your cadence. Conveniently, this extension is delivered "in the box" at /internal/extensions, so you do not have to change anything about your current Policy Checks workflow.
  • Learn more https://docs.liquibase.com/pro-extensions

Other Checks Enhancements

  • Pro users can suppress sql in reports with the new global property: --reports-suppress-sql=true
  • New checks-settings files can be created without CLI prompts by adding --force to checks show command
  • By popular demand, checks reports now show all checks run, including those not triggered.
  • We simplified the custom python check creation flow by removing the single-answer prompts/
  • Learn more https://docs.liquibase.com/policy-checks

[OSS]

Liquibase capability enhancements

... (truncated)

Changelog

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

Liquibase 4.31.0 is a major release

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

[PRO] Changelog

New Features

Bug Fixes

Security, Driver and Other Updates

[OSS] Changelog

New Features

... (truncated)

Commits
  • 11ef37b DAT-19398 DevOps :: Fix Liquibase Checks versioning in the tarball to match t...
  • 9ff9bef chore: FILES FOR 4.31.0 RELEASE (#6637)
  • 509e575 Handle @ symbol when executing PostgreSQL SET SEARCH_PATH (#6630)
  • 26b1294 DAT-18331 PRO: integrate checks extension into tarball/zip, not mac os dmg in...
  • d4250c0 undo UUID-ing of deployment ID (DAT-19367) (#6629)
  • 4cd3509 liquibase-maven-plugin: Allow null arguments to `ConfiguredValueModifierFac...
  • e68abdc DAT-19082: Fix issue with losing changed datatype attributes when one datatyp...
  • 40ef1af chore: rollback test count changes as they are failing for master (#6624)
  • 4ac1250 fix: test counts in master (#6623)
  • 2f474fb Implement logic to selectively include/exclude columns in generate-changelog ...
  • Additional commits viewable in compare view

Updates org.liquibase:liquibase-maven-plugin from 4.24.0 to 4.31.0

Release notes

Sourced from org.liquibase:liquibase-maven-plugin's releases.

Liquibase v4.31.0

Liquibase 4.31.0 is a major release

[!IMPORTANT] Liquibase 4.31.0 contains an expanded Checks Extension, and so the artifact size has increased.

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

⚠️ Breaking Change

Changesets with entirely blank IDs will now fail validation. This change improves the reliability and diagnosability of database changes, and enforces the best-practices set forth in documentation and training.

This validation does not apply to changesets that have already been deployed. However, any changesets marked as runOnChange or runAlways will fail validation if they have an empty changeset ID.

UPDATE: Reported Problems with LogicalFilePath

A few OSS users have reported a logicalfilepath bug, described below. This update aims to highlight potential trouble for users who meet three specific conditions:

  1. Use Liquibase 4.31.0
  2. Use the logicalfilepath attribute with different values at changelog and changeset levels
  3. Use include/includeAll to nest changelogs

The Bug The standard Liquibase practice is to accept the attribute closest to the changeset. But in 4.31.0, the parent logicalfilepath value will be used in DBCL/DBCLH as the changelogfilepath value.

What Next? If your workflow meets the conditions mentioned above, please avoid upgrading to version 4.31.0. The issue will be resolved in the upcoming 4.31.1 release.

Notable Changes

[PRO]

New Checks extension delivered in the box

  • Policy Checks are undoubtedly one of Liquibase Pro's stickiest capabilities, for which we continually add database platforms, new checks, and customizations. But to get these developments, users would need to download and upgrade to the latest Liquibase. Not any more! With this new checks extension, you can deploy the latest Policy Checks powers by optionally upgrading just the Check Extension on your cadence. Conveniently, this extension is delivered "in the box" at /internal/extensions, so you do not have to change anything about your current Policy Checks workflow.
  • Learn more https://docs.liquibase.com/pro-extensions

Other Checks Enhancements

  • Pro users can suppress sql in reports with the new global property: --reports-suppress-sql=true
  • New checks-settings files can be created without CLI prompts by adding --force to checks show command
  • By popular demand, checks reports now show all checks run, including those not triggered.
  • We simplified the custom python check creation flow by removing the single-answer prompts/
  • Learn more https://docs.liquibase.com/policy-checks

[OSS]

Liquibase capability enhancements

... (truncated)

Changelog

Sourced from org.liquibase:liquibase-maven-plugin's changelog.

Liquibase 4.31.0 is a major release

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

[PRO] Changelog

New Features

Bug Fixes

Security, Driver and Other Updates

[OSS] Changelog

New Features

... (truncated)

Commits
  • 11ef37b DAT-19398 DevOps :: Fix Liquibase Checks versioning in the tarball to match t...
  • 9ff9bef chore: FILES FOR 4.31.0 RELEASE (#6637)
  • 509e575 Handle @ symbol when executing PostgreSQL SET SEARCH_PATH (#6630)
  • 26b1294 DAT-18331 PRO: integrate checks extension into tarball/zip, not mac os dmg in...
  • d4250c0 undo UUID-ing of deployment ID (DAT-19367) (#6629)
  • 4cd3509 liquibase-maven-plugin: Allow null arguments to `ConfiguredValueModifierFac...
  • e68abdc DAT-19082: Fix issue with losing changed datatype attributes when one datatyp...
  • 40ef1af chore: rollback test count changes as they are failing for master (#6624)
  • 4ac1250 fix: test counts in master (#6623)
  • 2f474fb Implement logic to selectively include/exclude columns in generate-changelog ...
  • Additional commits viewable in compare view

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 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)

@dependabot
build(deps): bump liquibase.version from 4.24.0 to 4.31.0 in /backend
f9589eb 
Bumps `liquibase.version` from 4.24.0 to 4.31.0.

Updates `org.liquibase:liquibase-core` from 4.24.0 to 4.31.0
- [Release notes](https://github.com/liquibase/liquibase/releases)
- [Changelog](https://github.com/liquibase/liquibase/blob/master/changelog.txt)
- [Commits](liquibase/liquibase@v4.24.0...v4.31.0)

Updates `org.liquibase:liquibase-maven-plugin` from 4.24.0 to 4.31.0
- [Release notes](https://github.com/liquibase/liquibase/releases)
- [Changelog](https://github.com/liquibase/liquibase/blob/master/changelog.txt)
- [Commits](liquibase/liquibase@v4.24.0...v4.31.0)

---
updated-dependencies:
- dependency-name: org.liquibase:liquibase-core
  dependency-type: direct:production
  update-type: version-update:semver-minor
- dependency-name: org.liquibase:liquibase-maven-plugin
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file java labels Feb 11, 2025
@c3s4rfred
Copy link
Contributor

c3s4rfred commented Feb 14, 2025

Can't be done for now, return execution error with changesets that performs insertions in logstash filters table.

@c3s4rfred c3s4rfred closed this Feb 14, 2025
@dependabot @github
Copy link
Contributor Author

dependabot bot commented on behalf of github Feb 14, 2025

OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.

@dependabot dependabot bot deleted the dependabot/maven/backend/liquibase.version-4.31.0 branch February 14, 2025 15:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@c3s4rfred