chore: bump jackson.version from 2.19.2 to 2.20#2097
Conversation
|
CI errors with The correct version name is 2.20**.0** with a zero at the end. |
|
@dependabot recreate |
Bumps `jackson.version` from 2.19.2 to 2.20. Updates `com.fasterxml.jackson.core:jackson-databind` from 2.19.2 to 2.20 Updates `com.fasterxml.jackson.core:jackson-core` from 2.19.2 to 2.20 Updates `com.fasterxml.jackson.core:jackson-annotations` from 2.19.2 to 2.20 - [Commits](https://github.com/FasterXML/jackson/commits) Updates `com.fasterxml.jackson.datatype:jackson-datatype-jsr310` from 2.19.2 to 2.20 --- updated-dependencies: - dependency-name: com.fasterxml.jackson.core:jackson-databind dependency-version: '2.20' dependency-type: direct:development update-type: version-update:semver-minor - dependency-name: com.fasterxml.jackson.core:jackson-core dependency-version: '2.20' dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: com.fasterxml.jackson.core:jackson-annotations dependency-version: '2.20' dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: com.fasterxml.jackson.datatype:jackson-datatype-jsr310 dependency-version: '2.20' dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dcefaa9 to
2105f8e
Compare
|
There is an incosistency in how Jackson names release version. Jackson annotations uses In the related issue, it is recommended to migrate to the Jackson BOM: https://github.com/FasterXML/jackson-bom Let me do this here since it is a more stable approach in updating jackson version so that they are compatible with each other. Comment in Jackson BOM: |
|



Bumps
jackson.versionfrom 2.19.2 to 2.20.Updates
com.fasterxml.jackson.core:jackson-databindfrom 2.19.2 to 2.20Updates
com.fasterxml.jackson.core:jackson-corefrom 2.19.2 to 2.20Updates
com.fasterxml.jackson.core:jackson-annotationsfrom 2.19.2 to 2.20Commits
Updates
com.fasterxml.jackson.datatype:jackson-datatype-jsr310from 2.19.2 to 2.20Dependabot 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)