Bump liquibase-core from 3.8.9 to 3.9.0

[dependabot-preview]

Bumps liquibase-core from 3.8.9 to 3.9.0.

Release notes

Sourced from liquibase-core's releases.

v3.9.0

Liquibase 3.9.0 extends diff command with Pro capability

Liquibase Pro can help you automate drift detection at scale in your database schemas with a new structured and machine readable diff output as json. This additional capability is an Pro extension to the existing community command "diff", and is invoked with a new --format option $> liquibase diff --format=json

This outputs a JSON structured object listing the differences between two databases (as configured in your liquibase.properties or Maven POM file under the "url" and "referenceUrl" keys.) By default, the result is output to STDOUT, which provides you with maximum flexibility to pipe the result into other tools or a processing pipeline. You can also have the output delivered to a file, using the "--outputFile=<filename>" global parameter, as in $> liquibase --outputFile=myfile.json diff --format=json

Whether you choose STDOUT or a collection of files, you can then process this data to generate reports, to trigger actions, from alerts to diffChangeLogs, to updates, or whatever make sense for how you use Liquibase.

Changelog

Sourced from liquibase-core's changelog.

Liquibase Core Changelog

Changes in version 3.9.0 (2020.5.13)

• [Pro] New ""--format=json" argument for diff command

Changes in version 3.8.9 (2020.4.06)

• Fixed an issue with how Liquibase handles SMALLINT columns in PostgreSQL when generating a changelog.
• Improved generateChangeLog command to assume a diffTypes that includes "data" when the dataOutputDirectory parameter is used. Most users looking to export data as part of generateChangeLog can now simply use the dataOuputDirectory parameter without needing to specify diffTypes.
• Enabled the use of the --schemas parameter to work on either side of the snapshot command.
• Enabled generatechangelog in PostgreSQL to correctly order create, function, and trigger statements.
• Improved the use of dblink objects when using diff command.

Changes in version 3.8.8 (2020.3.19)

• rollbackOneChangeSetSQL now works correctly with the Liquibase Maven plugin.
• Liquibase Pro no longer generates procedural code with incorrect SQL syntax when running generateChangeLog against a MySQL database.

Changes in version 3.8.7 (2020.2.21)

• New liquibase history command
• [Pro] New liquibase rollbackOneUpdate command
• PR#927 CompositeClassLoader does not implement getResource(String)
• liquibase --help was improved to include missing commands and correct information

Changes in version 3.8.6 (2020.2.6)

• New graphical installer for Windows and Mac
• New examples directory with sample xml and sql changelogs and test h2 database
• [Pro] New RollbackOneChangeSet and RollbackOneChangeSetSQL commands
• Updated default Mysql driver to com.mysql.cj.jdbc.Driver
• Removed non-jdbc compatible "SET DEFINE OFF" from generated SQL on Oracle
• Fixed --excludeObjects/--includeObjects arguments in diff

Changes in version 3.8.5 (2020.1.13)

• Fixes issue in which Liquibase did not add DESC to an id column
• CLI once again accepts sqlFile, delimiter, rollbackScript, and outputSchemaAs arguments
• Fixes Stored Procedure whitespace impacting update calls
• Fixes generateChangelog failure when there are missing NOT NULL constraints.
• Fixes updateSQL, which was not including schemaName for package bodies.
• Fixes bug in which Liquibase was not always capturing create package body while generating changeLog
• Liquibase CLI now gives a more useful error message when an invalid character is passed to a command.
• Fixes an MSSQL issue, which threw an exception when doing diff/diffChangeLog between offline connections (such as when snapshotting json files)
• Fixes an MSSQL issue, which incorrectly generated datetime data type column when usingdiff & diffChangeLog
• Liquibase Maven plugin fails while executing/using "diff" and "generateChangeLog" with PostgreSQL)

Changes in version 3.8.4 (2019.12.23)

• Fixed a 'Class not Found' exception error when using Java +9.
• Fixed a 'Cannot Use Default Schema Name' error when users diff against an SQL Server snapshot file.

... (truncated)

Commits

• 9cccc14 Merge pull request #1151 from liquibase/DAT-4618
• 4266fa1 Missed an example file rename for DAT-4618
• 23f0147 Added 3.9.0 changelog note
• a8b1104 Updated version number for 3.9.0
• 78b5713 Merge remote-tracking branch 'origin/3.9.x' into 3.9.x
• 26245d4 Updated version number for 3.9.0
• b1c5d21 Merge pull request #1145 from liquibase/DAT-4618
• 9614a5d Fix some issues in Getting Started documentation
• d061765 Merge pull request #1127 from liquibase/DAT-4575
• 4a8a306 Merge pull request #1090 from liquibase/DAT-4347
• 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 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 use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)