[DCJ-400-gradle]: Bump org.liquibase.gradle from 2.2.1 to 3.0.0 #1765
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps org.liquibase.gradle from 2.2.1 to 3.0.0. --- updated-dependencies: - dependency-name: org.liquibase.gradle dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
|
The following labels could not be found: |
dependabot
bot
requested review from
rushtong and
okotsopoulos
and removed request for
a team
|
@dependabot rebase |
|
Looks like this PR is already up-to-date with develop! If you'd still like to recreate it from scratch, overwriting any edits, you can request |
|
okotsopoulos
added
dependency
| classpath('io.swagger.codegen.v3:swagger-codegen:3.0.52') | ||
| // Required for gradle liquibase plugin | ||
| classpath ('org.liquibase:liquibase-core:4.26.0') |
There was a problem hiding this comment.
Note for reviewers:
- Adding this classpath to the buildscript is new requirement with gradle liquibase 3.0.0
- Ideally, we wouldn't pin the version of liquibase-core. However, the version appears to be required when defining the classpath. Additionally, we need to pin the version for the implementation of liquibase-core, or it would default to 4.24.0.
There was a problem hiding this comment.
Good shout -- I will revisit this as part of our latest bulk version update to see if it's still needed.
When we upgrade Spring Boot to latest -- 3.3.2 -- we'll get liquibase versioned at 4.27.0, do you think that might allow us to remove the version here? https://github.com/spring-projects/spring-boot/blob/v3.3.2/spring-boot-project/spring-boot-dependencies/build.gradle#L1066
There was a problem hiding this comment.
I'm not sure, it wouldn't build without a version here. But, maybe I was just missing something.
|
I also confirmed that at least the ./gradlew dropall command still works! |
Bumps org.liquibase.gradle from 2.2.1 to 3.0.0.
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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)