Bump liquibase-core from 4.3.2 to 4.3.3 #31
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps liquibase-core from 4.3.2 to 4.3.3.
Release notes
Sourced from [liquibase-core's releases](https://github.com/liquibase/liquibase/releases).
Changelog
Sourced from [liquibase-core's changelog](https://github.com/liquibase/liquibase/blob/master/changelog.txt).
... (truncated)
Commits
3e83d9b
Incremented version number31d7bac
Merge pull request [#1788](https://github-redirect.dependabot.com/Fix changeLogSync issue when Hub settings exist DAT-6938 liquibase#1788) from liquibase/DAT-6938431b960
Added 4.3.3 changelog.txt entry5c22767
Handle possible null objects in the reference or comparison lists0465102
- Better handle not found liquibase.properties files in maven.a844c3c
With diffToChangeLog, insert Columns after the last Table, and befored85937f
Handle ordering issue6e50249
Attempt to make sure addColumn occurs before it is used in diff0ee264f
[#1366](https://github-redirect.dependabot.com/DateTimeType.java:38 NullPointerException (liquibase 4.0.0) liquibase#1366) DateTimeType.java:38 NullPointerException5b3c83c
Fix changeLogSync issue when Hub settings existDependabot 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 readmeAdditionally, you can set the following in your Dependabot dashboard:
┆Issue is synchronized with this Jira Bug by Unito