Bump liquibase.version from 4.9.0 to 4.9.1

[dependabot]

Bumps liquibase.version from 4.9.0 to 4.9.1.
Updates liquibase-core from 4.9.0 to 4.9.1

Release notes

Sourced from liquibase-core's releases.

v4.9.1

Liquibase 4.9.1 patch release

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

Notable Changes

[PR#2666] [nvoxland] Liquibase 4.9.1 release is a patch release that fixes the MANIFEST.MF location in the liquibase.jar file for tools that require the MANIFEST.MF file to be the first entry in the jar archive. If the MANIFEST.MF file is not the first entry, java.util.jar.JarInputStream#getManifest() reading the MANIFEST.MF file will not return the manifest information appropriately. The PR fixes issue #2648.

[Issue#2672] Addresses the remaining OSGi-related packaging problems to fully restore Liquibase support in OSGi environments.

Fixes

[PR#2651] Fixed the issue with a malicious software alert for the Liquibase macOS Installer preventing from proceeding with the installation. [DAT-9524]

[PR#2643] Fixed an issue in snapshot on PostgreSQL where non-integer datatypes that used a default value with a sequence would not be handled correctly [DAT-8670]

[PR#2691] Fixed invalid JSON in the example-changelog.json file [DAT-9893]

Full Changelog: liquibase/liquibase@v4.9.0...v4.9.1

Get Certified

Learn all the Liquibase fundamentals from free online courses by Liquibase experts and see how to apply them in the real world at https://learn.liquibase.com/.

Read the Documentation

Please check out and contribute to the continually improving docs, now at https://docs.liquibase.com/.

Meet the Community

Our community has built a lot. From extensions to integrations, you’ve helped make Liquibase the amazing open source project that it is today. Keep contributing to making it stronger:

• Contribute code
• Make doc updates
• Help by asking and answering questions
• Set up a chat with the Product team

Thanks to everyone who helps make the Liquibase community strong!

Changelog

Sourced from liquibase-core's changelog.

Liquibase 4.9.1 patch release

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

Notable Changes

[PR#2666] [nvoxland] Liquibase 4.9.1 release is a patch release that fixes the MANIFEST.MF location in the liquibase.jar file for tools that require the MANIFEST.MF file to be the first entry in the jar archive. If the MANIFEST.MF file is not the first entry, java.util.jar.JarInputStream#getManifest() reading the MANIFEST.MF file will not return the manifest information appropriately. The PR fixes issue #2648.

[Issue#2672] Addresses the remaining OSGi-related packaging problems to fully restore Liquibase support in OSGi environments.

Fixes

[PR#2651] Fixed the issue with a malicious software alert for the Liquibase macOS Installer preventing from proceeding with the installation. [DAT-9524]

[PR#2643] Fixed an issue in snapshot on PostgreSQL where non-integer datatypes that used a default value with a sequence would not be handled correctly [DAT-8670]

[PR#2691] Fixed invalid JSON in the example-changelog.json file [DAT-9893]

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

• f669da2 Merge pull request #2691 from liquibase/DAT-9893
• 2260bac fix invalid JSON in example-changelog.json
• 41b1e2f Release Logic Bugfixes (#2685)
• 0f95718 preserve default value of invalid autoincrement column types in Postgres (DAT...
• 053c3a2 Updating re-version.sh to run under macos
• a7c9171 Updating re-version.sh to run under macos
• 50bfc09 Updating re-version.sh to run under macos
• 95d303b Updating re-version.sh to run under macos
• 6a4d230 Updating re-version.sh to run under macos
• 587eb65 Preparing for 4.9.1 release
• Additional commits viewable in compare view

Updates liquibase-mongodb from 4.9.0 to 4.9.1

Commits

• See full diff in compare view

You can trigger a rebase of this PR 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)

[quarkus-bot]

Failing Jobs - Building 6f06493

Status	Name	Step	Failures	Logs	Raw logs
✔️	JVM Tests - JDK 11
✖	JVM Tests - JDK 17	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 17 #

- Failing: integration-tests/elytron-undertow 

📦 integration-tests/elytron-undertow

✖ io.quarkus.it.undertow.elytron.BaseAuthTest.testPost line 27 - More details - Source on GitHub

java.lang.AssertionError: 
1 expectation failed.
Expected status code <200> but was <500>.

[famod]

Failure is not related