![]() Fix tests because of output change from Postgres 9.6 to 15.DAT-13953: fix integration name log message for native tools by in liquibase/liquibase-pro#937.remove helper commands from help output (DAT-14674) by in #4207.Load properties from defaults-file fixing variable replacement for refactored commands by in #4204.Change the case of sys.extended_properties.SnowflakeDatabase allows catalog name in identifiers in #4092.Always use LockService from Factory when running command steps by in #4151.include changelog file when running status command from Liquibase class (DAT-14659) by in #4201.Move dbchangelog-4.21.xsd to liquibase-standard by in #4176.Fix addDefaultValue checksum calculation when providing schema name by in #4203.Fixed #3722 auto-increment column starting with a custom value no longer works with H2 v1 by in #4013.Fixes undesired change to CreateProcedureChange checksum generation by in #4161. ![]() Fix search path handle for PostgreSQL with JDBC connection with specified schema by in #4021.Fixed #3487 Provide precision and scale for currency database datatype and H2.Bump jacoco-maven-plugin from 0.8.9 to 0.8.10 by in liquibase/liquibase-pro#955.Bump jackson-dataformat-yaml from 2.14.2 to 2.15.0 by in liquibase/liquibase-pro#953.Bump jackson-module-jaxb-annotations from 2.14.2 to 2.15.0 by in liquibase/liquibase-pro#951.Bump jackson-annotations from 2.14.2 to 2.15.0 by in liquibase/liquibase-pro#950.Bump jackson-core from 2.14.2 to 2.15.0 by in liquibase/liquibase-pro#949.Bump logback-classic from 1.4.6 to 1.4.7 by in liquibase/liquibase-pro#947.Bump flatten-maven-plugin from 1.3.0 to 1.4.1 by in #4036.Bump maven-enforcer-plugin from 3.2.1 to 3.3.0 by in #4081.Bump maven-surefire-plugin from 2.22.2 to 3.0.0 by in #4113.update pro xsd and schema to 4.22 by in liquibase/liquibase-pro#971.DAT-14674: add help test for pro side by in liquibase/liquibase-pro#965.DAT- 13285:: Update stored logic checksum logic to match new OSS checksum logic for procedures by in liquibase/liquibase-pro#931.DAT-12568 pro license key automation by in liquibase/liquibase-pro#966.update pro key for test by in liquibase/liquibase-pro#962.MDC for update-testing-rollback by in liquibase/liquibase-pro#943.update pom.xml by in liquibase/liquibase-pro#929.DAT-13972: add rollback-on-error ability and its MDC to update-one-changeset command by in liquibase/liquibase-pro#934.Adding support for Postgresql-generated columns.Update release-published.yml by in #4206.Improve liquibase-core pom.xml handling (DAT-14546) by in #4169.DAT-13285 - Fix CheckSum generation issues + improvement by in #3914.However, for users who rely on the detection of a changed changeset or have complex workflows, it is recommended that you run liquibase clear-checksums with your current version BEFORE your first operation using the new 4.22.0 version against a database. No actions is required for the vast majority of users. New checksums are silently recalculated upon the initial run of Liquibase 4.22.0 or greater. The checksum changes in Liquibase version 4.22.0 a major change, which improves whitespace handling in views, procedures, Liquibase Pro stored logic objects, and more. If you are a Liquibase customer and believe you may be impacted by this issue, please open a ticket in our support portal at įull Changelog: v4.21.1.v4.22.0 Notable Changes We will soon provide more guidance on how to assess and remedy any potential impact for users who have already upgraded to Liquibase 4.22.0. If you have not upgraded to Liquibase 4.22.0, you are not impacted by this issue, or if you do not rely on runOnChange changesets which have changed before your upgrade. Specifically, currently undeployed changesets with the runOnChange=true attribute may not be deployed if they were present in the first execution of Liquibase 4.22.0 against a given target database. In some situations, the conversion to this new algorithm could result in eligible changes not being deployed to a target database. This version contains an updated algorithm for determining which changes Liquibase needs to deploy to a database. Note: We have removed the 4.22.0 release of Liquibase. Release Notes Liquibase 4.22.0 – May 11, 2023
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |