[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]
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/.
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:
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#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
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[bot]
commented
2 years ago
Bumps liquibase-core from 4.5.0 to 4.9.1.
Release notes
Sourced from liquibase-core's releases.
... (truncated)
Changelog
Sourced from liquibase-core's changelog.
... (truncated)
Commits
f669da2Merge pull request #2691 from liquibase/DAT-98932260bacfix invalid JSON in example-changelog.json41b1e2fRelease Logic Bugfixes (#2685)0f95718preserve default value of invalid autoincrement column types in Postgres (DAT...053c3a2Updating re-version.sh to run under macosa7c9171Updating re-version.sh to run under macos50bfc09Updating re-version.sh to run under macos95d303bUpdating re-version.sh to run under macos6a4d230Updating re-version.sh to run under macos587eb65Preparing for 4.9.1 releaseDependabot 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)