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.16.1 to 4.17.0 #57

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps liquibase-maven-plugin from 4.16.1 to 4.17.0.

Release notes

Sourced from liquibase-maven-plugin's releases.

v4.17.0

Liquibase v4.17.0

Notable Changes

  • [PRO] The liquibase flow command and flow files are available with a Pro license. It allows you to create portable, platform-independent workflows that can run across different tools without modifying each workflow.

  • [PRO] Pro license users can now integrate Amazon S3 with Liquibase. You can extend Liquibase to use remote file locations to enable secure, centralized file management.

  • [PRO] Pro license users can use searchpath to find files located on S3 that cannot be found by an absolute path.

API Breaking Changes

  • The liquibase.resource.ResourceAccessor APIs were updated to take advantage of the new liquibase.resource.Resource abstraction that was introduced. Code that USES the existing ResourceAccessor methods will continue to work as before with no changes, but if you have written custom implementations of ResourceAccessor there are new and changed methods to implement. For more information, see javadocs.liquibase.com

Enhancements

Fixes

Updates

Security Updates

... (truncated)

Changelog

Sourced from liquibase-maven-plugin's changelog.

Liquibase Core Changelog

Changes in version 4.17.0 (2022.10.05)

Notable Changes

  • [PRO] The liquibase flow command and flow files are available with a Pro license. It allows you to create portable, platform-independent workflows that can run across different tools without modifying each workflow.

  • [PRO] Pro license users can now integrate Amazon S3 with Liquibase. You can extend Liquibase to use remote file locations to enable secure, centralized file management.

  • [PRO] Pro license users can use searchpath to find files located on S3 that cannot be found by an absolute path.

API Breaking Changes

  • The liquibase.resource.ResourceAccessor APIs were updated to take advantage of the new liquibase.resource.Resource abstraction that was introduced. Code that USES the existing ResourceAccessor methods will continue to work as before with no changes, but if you have written custom implementations of ResourceAccessor there are new and changed methods to implement. For more information, see javadocs.liquibase.com

Enhancements

Fixes

Updates

... (truncated)

Commits
  • c9ceb05 Update changelog 4.17 (#3343)
  • d76db16 Created 4.17 dbchangelog.xml file (#3337)
  • 59ca536 Fix generateChangeLog and diffChangeLog logic to avoid including default sche...
  • 3c94c98 Ignore multiple jvm test for now
  • fca8f63 Added sonar warning suppression
  • b22e3d0 DAT-11407: replace backslashes in NotFoundResource URI (#3322)
  • 831ca99 Created new liquibase.resource.Resource interface (#3064)
  • 2a7ac9e Merge pull request #3310 from liquibase/dependabot/maven/org.yaml-snakeyaml-1.33
  • 8b759d7 Fixed createView handling of replaceIfExists=true when the string "replace" e...
  • c9dd8da Addition of liquibase.update() Enhancement Request #1614 (#1638)
  • 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)