Skip to content

Upgrade First Party Library Dependencies for Release 0.18

David Diederich requested to merge dependency-upgrade into release/0.18

This automated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release. The intent is to keep the OSDU projects utilizing the latest available code to ensure widespread usage and stability. However, any library that is older than the previous release will be left as-is, since the upgrade is likely to be more complicated. Furthermore, the upgrade should only be merged in the CI pipeline reports success.

If this MR has failed, we can spend a little time investigating to see if a trivial upgrade could achieve compatiblity to the new library. But significant upgrade efforts should not occur on this MR, as part of the release tagging process. Instead, significant work should be scheduled for a subsequent milestone.

Dependency Information Before the Upgrade

Branch: release/0.18
SHA:    eb79ab42caf333e3acc0756f6c5803f474ff21df
Maven:  0.18.0-SNAPSHOT
Maven Dependencies Root
os-core-common 0.18.0-rc3
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.13.4
(3rd Party) org.springframework.spring-webmvc 5.3.22

Dependency Information After the Upgrade

Branch: dependency-upgrade
SHA:    c3d208a06ab1865292173916fa9decbe7b83e0c0
Maven:  0.19.0-SNAPSHOT
Maven Dependencies Root
os-core-common 0.18.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.13.4
(3rd Party) org.springframework.spring-webmvc 5.3.22

Why is this a direct patch?

The default branch has already moved on to os-core-common 0.19.0-rc1. So, there's no benefit in merging this to the default branch (and it would undo work already started towards the next release), but we need it here for the 0.18 release.

Edited by David Diederich

Merge request reports