Update dependency org.liquibase:liquibase-core to v3.10.3

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.liquibase:liquibase-core (source)	3.8.8 -> 3.10.3

---

Release Notes

liquibase/liquibase

v3.10.3

Compare Source

Liquibase 3.10.3 is a bugfix release

Changes

This release merges many community-contributed pull requests. Thanks to everyone who helps make the Liquibase community strong!

• Fixed issue with includeAll not working with some spring-packaged jars https://github.com/liquibase/liquibase/pull/1140
• Fixed sequence snapshot in Postgresql https://github.com/liquibase/liquibase/pull/1372
• Fixed SERIAL/BIGSERIAL handling in Postgreql https://github.com/liquibase/liquibase/pull/1010
• SpringLiquibase bean can now take any ResourceAccessor implementation https://github.com/liquibase/liquibase/pull/936
• Fixed snapshot of TEXT types in MSSQL https://github.com/liquibase/liquibase/pull/1327
• Moved SQL logging from INFO to DEBUG https://github.com/liquibase/liquibase/pull/1258
• Minor XSD cleanup https://github.com/liquibase/liquibase/pull/1239
• Fixed handling of question marks in SQL for Postgresql https://github.com/liquibase/liquibase/pull/912
• Fixed handling of includeAll in maven https://github.com/liquibase/liquibase/pull/1332
• Do not expect access to v$session on Oracle https://github.com/liquibase/liquibase/pull/1422
• Allow spaces after -- comments in formatted SQL https://github.com/liquibase/liquibase/pull/781
• Fixed loadData support for enums in Postgresql https://github.com/liquibase/liquibase/pull/983
• Fixed CSV handling when last column is empty https://github.com/liquibase/liquibase/pull/1431
• Fixed SqlServer handling of computed columns in snapshot https://github.com/liquibase/liquibase/pull/1443
• Avoid broken PostgreSQL batch logic https://github.com/liquibase/liquibase/pull/1447

Special 3.10.3 shout-outs

Mike Olivas, mrgrew, Robert Reeves, FrankHoellering, Steven C. Saliman, thomas, Ruud Welling, Sudipto Sarkar, alexander.schuetz, ningyu, Wes Willard and others!

v3.10.2

Compare Source

Liquibase 3.10.2 is a bugfix release

Changes

This release merges many community-contributed pull requests. Thanks to everyone who helps make the Liquibase community strong!

• Dependency cycle error during generateChangeLog with --diffTypes=tables,columns,data
• liquibase maven:: unable to run tests on java > 8
• Add Banner in log out put that directs users to online resources.
• GH PR#​980 - fixed invalid carriage return coming from oracle ojdbc8 12.2.0.1
• GH PR#​976 - Changes databasechangelog sql to use legacy mode
• Add support for java.sql.Types.TIMESTAMP_WITH_TIMEZONE (CORE-3525)
• GH PR#​929 - Fix #CORE-3493 Inconsistent resolution of ChangeLogParameters in liqu…
• GH PR#​744 - Informix data type generation with Default Value cause
• GH PR#​1176 - Add MariaDB sequence support to the 3.10.x branch
• GH PR#​1177 - CORE-3643: fixed the 'shouldValidateX' methods in the Constraints
• GH PR#​1201 - H2 unknown reserved word

v3.10.1

Compare Source

Liquibase 3.10.1 is a bugfix release

Changes

• GH PR#​913 - [CORE-3471] Fixed NPE in LiquibaseUtil when MANIFEST.MF doesn't contain Bundle-Version or Build-Time
• GH PR#​917 - [Core 3463] Fix for validateX attributes of constraintsConfig
• GH PR#​919 - Fixed issued with bundling in shaded jars
• GH PR#​941 - [CORE-3520] Add support for ALWAYS generation type with PostgreSQL auto-increment column.
• GH PR#​946 - [CORE-3524] Prevent auto-increment column silently failing on Oracle.
• GH PR#​949 - [CORE-3526] TABLE is a reserved keyword in H2database since 1.4.197
• GH PR#​963 - [CORE-3556] No default values for changes' properties
• GH PR#​965 - [CORE-3558] Unique constraint name is ignored when using the addColumn change
• GH PR#​970 - Fix Java 1.9+ versions require jaxb as separate dependency
• GH PR#​971 - Add Class-Path entry to the manifest file to simplify command line execution
• GH PR#​975 - NULL date value in prepared statement requires type in MSSQL
• GH PR#​986 - XMLSerializer: Correct Map value serialization
• GH PR#​993 - Improve ChangeFactory initialization time
• GH Issue#​1035 - Change how Liquibase produces debug logs
• GH Issue#​1051 - Update liquibase-core.jar to exclude ServiceLoader files
• GH PR#​1053 - Update liquibase_autocomplete.shape
• GH PR#​1059 - Allow multiple column unique constraints on table creation.
• GH Issue#​1069 - Patch Liquibase Runner plugin for Jenkins
• GH Issue#​1070 - Enable --help without databse connection
• GH PR#​1082 - Correct include bash script
• GH PR#​1096 - Fix sequence statement generation for PostgreSQL <= 9.4
• GH Issue#​1104 - Fix maven-liquibase offline diff to prevent errors
• GH Issue#​1113 - Fix schema name using "--defaultSchemaName" on a non-default schema
• GH PR#​1120 - LiquibaseServletListener.contextInitialized() improved with Embedded Derby
• GH Issue#​1220 - Fix how JAVA_HOME env variable is handled

This release merges many community-contributed pull requests. Thanks to everyone who helps make the Liquibase community strong!

v3.10.0

Compare Source

Liquibase 3.10.0 offers SQL Plus integration, Custom Executor extensibility, Complementary Bash script

SQL Plus Integration and the new "runWith" attribute

There are occasions when the Liquibase in-built JDBC connector has trouble processing highly-specialized or variable-rich SQL, and a more purpose-built tool, like SQL Plus or other executor, is required.

For Liquibase Community and Pro users, we are introducing an optional changeset attribute, called runWith="<executor>" which allows you to specify an “executor” to run your SQL. This new capability works with changesets in Formatted SQL, XML, JSON or YAML changelogs which call inline SQL or sqlFile tagged changesets. For Pro users, there is also a new liquibase.sqlplus.conf file, which lives alongside your liquibase.properties or POM file, where you can optionally specify some useful key-value pairs for configuring your executor.

As a Liquibase Pro user, employ the new SQLPlus integration by simply adding runWith="sqlplus" to a changeset, and have SQL Plus in your PATH (or configure it in the accompanying liquibase.sqlplus.conf file). It’s now that easy to run your complex or specialized SQL changesets with SQL Plus.

Integrate your own executor

As exciting, and true to open-source and open-extensibility, Liquibase Community users can now write their own classes to integrate their own executor. Say, for example, you need an encrypted JDBC tool, which you want to call as “ejdbc” from your changeset? Simply follow the included example so you can take advantage of this new feature:

• Write and configure the classes to call your tool
• Add runWith="ejdbc" to select changesets to process them with your custom executor

New Auto-complete Bash Script

In the Liquibase 3.10 release, you will also find a new bash script for MacOS / and Git Bash for Windows users called .liquibase-completion-mac.bash. This script adds some ease of use to the CLI, including auto-complete of commands and and auto-rollout of parameters. This is a single bash script that will not affect any core Liquibase code, and can live alongside the existing bash script which has and will continue to ship with Liquibase.

v3.9.0

Compare Source

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.

v3.8.9

Compare Source

Bug Fixes & Improvements

For both Liquibase Community and Pro users, the following bugs were fixed in version 3.8.9:

• Fixed an issue with how Liquibase handles SMALLINT on 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.
• The --schemas parameter now works 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.

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by Mend Renovate. View repository job log here.