Liquibase 4.29.1 .zip files: Restored to standard directory structure
This release correctly places Liquibase .zip files inside liquibase-4.29.1 directory to match Pre-4.29.0 directory structure.
Big Query Extension: using Liquibase Pro with Google Big Query
With Liquibase 4.29.1, Google BigQuery is now supported as an ‘out of the box’ database enabling users to more quickly achieve value. Also included is support for Liquibase Pro features such as Flows, Policy Checks, and Reports with Google BigQuery so that users will have the efficiency and productivity benefits of Liquibase Pro when working with the platform.
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/.
Liquibase 4.29.1 patches a pom mismatch in the Liquibase BigQuery Commercial Extension.
Liquibase 4.29.1 resolves an issue with the zip distribution where all files were incorrectly placed inside liquibase-4.29.1 directory. This update ensures proper file organization and installation.
[!IMPORTANT]
Liquibase 4.29.0 contains several New Capabilities and Notable Enhancements for Liquibase Pro users: Python-based Custom Policy Checks and a new Big Query extension.
[!NOTE]
See the Liquibase 4.29.0 Release Notes for the complete set of release information.
Notable Changes
[PRO]
Custom Policy Checks: Create and run Python-based checks which fit your specific needs.
Liquibase checks have been opened to the world of Python development! With this release, you can point your custom checks to your custom Python scripts to solve your nuanced conditions for better risk mitigation, compliance, code quality, security, and more.
Big Query Extension: using Liquibase Pro with Google Big Query
With Liquibase 4.29.0, Google BigQuery is now supported as an ‘out of the box’ database enabling users to more quickly achieve value. Also included is support for Liquibase Pro features such as Flows, Policy Checks, and Reports with Google BigQuery so that users will have the efficiency and productivity benefits of Liquibase Pro when working with the platform.
Liquibase 4.29.1 .zip files: Restored to standard directory structure
This release correctly places Liquibase .zip files inside liquibase-4.29.1 directory to match Pre-4.29.0 directory structure.
Big Query Extension: using Liquibase Pro with Google Big Query
With Liquibase 4.29.1, Google BigQuery is now supported as an ‘out of the box’ database enabling users to more quickly achieve value. Also included is support for Liquibase Pro features such as Flows, Policy Checks, and Reports with Google BigQuery so that users will have the efficiency and productivity benefits of Liquibase Pro when working with the platform.
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/.
Liquibase 4.29.1 patches a pom mismatch in the Liquibase BigQuery Commercial Extension.
Liquibase 4.29.1 resolves an issue with the zip distribution where all files were incorrectly placed inside liquibase-4.29.1 directory. This update ensures proper file organization and installation.
[!IMPORTANT]
Liquibase 4.29.0 contains several New Capabilities and Notable Enhancements for Liquibase Pro users: Python-based Custom Policy Checks and a new Big Query extension.
[!NOTE]
See the Liquibase 4.29.0 Release Notes for the complete set of release information.
Notable Changes
[PRO]
Custom Policy Checks: Create and run Python-based checks which fit your specific needs.
Liquibase checks have been opened to the world of Python development! With this release, you can point your custom checks to your custom Python scripts to solve your nuanced conditions for better risk mitigation, compliance, code quality, security, and more.
Big Query Extension: using Liquibase Pro with Google Big Query
With Liquibase 4.29.0, Google BigQuery is now supported as an ‘out of the box’ database enabling users to more quickly achieve value. Also included is support for Liquibase Pro features such as Flows, Policy Checks, and Reports with Google BigQuery so that users will have the efficiency and productivity benefits of Liquibase Pro when working with the platform.
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 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
liquibase.versionfrom 4.24.0 to 4.29.1. Updatesorg.liquibase:liquibase-corefrom 4.24.0 to 4.29.1Release notes
Sourced from org.liquibase:liquibase-core's releases.
... (truncated)
Changelog
Sourced from org.liquibase:liquibase-core's changelog.
... (truncated)
Commits
e0c7137chore: Release notes (#6147)1a057d1DAT-18308 DevOps :: Extensions are built against liquibase 0-SNAPSHOT (#6146)ab2ee6bDAT-18308 DevOps :: Extensions are built against liquibase 0-SNAPSHOT (#6144)54744c8chore: adding 4.29.1 changes7e83bbccore: add breaking change to changelog (#6127)a6ff4aachore: re-enable releasing from master branch (#6124)5a3fa21chore: reversion liquibase-cli (#6121)d23ee58Liquibase 4.29.0 files (#6120)0fd943dBump org.apache.maven.plugins:maven-surefire-plugin from 3.3.0 to 3.3.1 (#6090)c7d6b1eRemove unneeded inclusion of commons-io in liquibase-core pom.xml (#6117)Updates
org.liquibase:liquibase-maven-pluginfrom 4.24.0 to 4.29.1Release notes
Sourced from org.liquibase:liquibase-maven-plugin's releases.
... (truncated)
Changelog
Sourced from org.liquibase:liquibase-maven-plugin's changelog.
... (truncated)
Commits
e0c7137chore: Release notes (#6147)1a057d1DAT-18308 DevOps :: Extensions are built against liquibase 0-SNAPSHOT (#6146)ab2ee6bDAT-18308 DevOps :: Extensions are built against liquibase 0-SNAPSHOT (#6144)54744c8chore: adding 4.29.1 changes7e83bbccore: add breaking change to changelog (#6127)a6ff4aachore: re-enable releasing from master branch (#6124)5a3fa21chore: reversion liquibase-cli (#6121)d23ee58Liquibase 4.29.0 files (#6120)0fd943dBump org.apache.maven.plugins:maven-surefire-plugin from 3.3.0 to 3.3.1 (#6090)c7d6b1eRemove unneeded inclusion of commons-io in liquibase-core pom.xml (#6117)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