schemacrawler / SchemaCrawler-Report-Maven-Plugin

Generate SchemaCrawler reports for Maven generated project websites
Eclipse Public License 2.0
8 stars 6 forks source link

Bump liquibase-maven-plugin from 4.8.0 to 4.9.0 #27

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps liquibase-maven-plugin from 4.8.0 to 4.9.0.

Release notes

Sourced from liquibase-maven-plugin's releases.

v4.9.0

Liquibase 4.9.0 release

Please report any issues to https://github.com/liquibase/liquibase/issues.

Notable Changes

Liquibase 4.9.0 introduces the following functionality:

  • [PRO] Quality Checks JSON object so that your application can easily parse through the Liquibase output [DAT-9094] For more information, see Quality Checks JSON Object.
  • Quality checks for Maven - checks.run and checks.show goals [DAT-9033] [DAT-9034] For more information, see Maven checks.run and Maven checks.show.
  • [PR#2558] [kavya-shastri] [Breaking Change]The change in the usage of the Liquibase global configuration for the secureParsing parameter to prevent the entity resolver from scanning the network for missing XSDs. If you reference an XSD other than one from Liquibase and have never stored them in your classpath, Liquibase will no longer automatically download and use the XSD from the internet for security reasons. The default value for secureParsing is true, but you can set it to false in any of the Liquibase configuration locations. For more information, see XSD support.
  • [PR#2529] [Krzysztof Sierszeń] [LB-1781] The uniqueConstraintExists precondition to check for the existence of unique constraints before running the update. You can check the constraint by constraint name or columns:
<preConditions>
    <uniqueConstraintExists constraintName="uq_constraint_name" tableName="test_table"/>
</preConditions>
<preConditions>
    <uniqueConstraintExists tableName="test_table" columnNames="first_name, last_name"/>
</preConditions>
  • [PR#2339] [nvoxland] [Toukite] The support for running the Liquibase Servlet listener in application servers built on the Jakarta Servlet specification and not the Java Servlet specification. To use the new listener, specify the following tag:
<listener>
    <listener-class>liquibase.integration.servlet.LiquibaseJakartaServletListener</listener-class>
</listener>

The PR fixes issue #2298.

Enhancements

  • [PR#2434] [Balázs Dési] Added the Maven validate goal to maven-liquibase-plugin to provide access to the existing Liquibase validate command and be available not only in CLI, but also in Maven For more information, see Maven validate.
  • Added the ability to use sqlcmd on an instance with multiple databases [DAT-9513] For more information, see Using the SQLCMD integration and runWith attribute with Liquibase Pro and MSSQL Server.
  • Added support for Liquibase, Spring Boot, and SQL Plus run with Kerberos [DAT-9409] For more information, see Using Liquibase and Spring Boot with SQL Plus and Kerberos Authentication.
  • [PR#2561] [Wesley Willard] Added the --schemas argument to the snapshot command to be able to compare a multi-schema database to its snapshot [DAT-9433]
  • [PR#2606] [Wesley Willard] Added a best practice message for the generate-changelog command so that you can check if the splitStatements attribute works for your environment when generating formatted SQL changelogs [DAT-9327]
  • Added the StripComments attribute for the SQLUserDefinedPatternCheck quality check to choose the code that the SQLUserDefinedPatternCheck searches, including the option for the commented code. The StripComments attribute strips comments from SQL before searching for the string. The default value is N (no). [DAT-9098]
  • [PR#2273] [Tsvi Zandany] Added the autocomplete option for quality checks commands running on macOS

Fixes

  • [PR#2542] [nvoxland] Fixed the --should-snapshot-data CLI parameter to be preserved when the --data-output-directory property is not specified in the command
  • [PR#2330] [Inane Mohammed] Fixed the issue with checking the referenceSnapshot parameter instead of referenceDatabase for the potential null value
  • [PR#2521] [Steven Massaro] Added a label, context, and comment to the example-changelog.sql file that comes with the Liquibase installation package [DAT-9325]
  • [PR#2556] [nvoxland] Fixed the CockroachDB processes so that Liquibase checks the URL first rather than proceeding with SQL calls
  • [PR#2569] [Clarence Dimitri CHARLES] Made FormattedSqlChangeLogParser to be reusable for extensions
  • [PR#2377] [devorgpl] Fixed the issue with updating statements when the onlyUpdate attribute is false in the loadUpdateData Change Type for HSQL
  • [PR#1908] [Emiliano Capoccia] Fixed the issue with retrieving the CockroachDB version. As part of the fix, Liquibase generates version-specific autoincrement SQL statements for CockroachDB identity columns:
    • SMALLSERIAL, SERIAL, and BIGSERIAL for versions earlier than 21.2

... (truncated)

Changelog

Sourced from liquibase-maven-plugin's changelog.

Liquibase Core Changelog

Changes in version 4.9.0 (2022.03.17)

Notable Changes

Liquibase 4.9.0 introduces the following functionality:

  • [PRO] Quality checks output in a JSON format
  • Quality checks for Maven - checks run and checks show goals
  • [PR#2558] [kavya-shastri] The extension of the usage of the Liquibase global configuration for the secureParsing parameter to prevent the entity resolver from falling back to looking on the network for missing XSDs. If you reference an XSD other than one of Liquibase, Liquibase will no longer automatically download the XSD from the internet and use it. The default value for secureParsing is true, but you can override it in any of the Liquibase configuration locations. For more information, see the Example Changelogs: XML Format documentation.
  • [PR#2529] [Krzysztof Sierszeń] [LB-1781] The uniqueConstraintExists precondition to check for the existence of unique constraints before running the update. You can check the constraint by constraint name or columns:

... (truncated)

Commits
  • 2330bc4 Merge pull request #2646 from liquibase/update-changelogtxt-4.9.0
  • 2174d30 updated changelog txt
  • c74a333 Merge pull request #2645 from liquibase/update-changelogtxt-4.9.0
  • 477ba0a update changelog 4.9.0
  • 0713941 DAT-9524 test without appleId cli parameter
  • 2724443 DAT-9524 update install4j project config
  • c40e147 DAT-9524 add debug logging for install4j
  • e19e831 Merge pull request #2642 from liquibase/github-action-DAT-9524
  • 8d2d793 github-action-DAT-9524 add apple_id creds for installer notarizing
  • 4a9f8e0 Created dbchangelog xsd (#2638)
  • 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 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 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)