Skip to content

Upgrade First Party Library Dependencies for Release 0.20

David Diederich requested to merge dependency-upgrade into master

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: master
SHA:    31a5fcb19118b8ae544c9c6273953c944adc9161
Maven:  0.21.0-SNAPSHOT
Maven Dependencies Root
os-core-common 0.19.0
(3rd Party) org.yaml.snakeyaml 1.33 
Critical: Found Vulnerable Snake YAML dependency (<2.0)
└─ _Root_
└─ org.opengroup.osdu.os-core-lib-ibm == 0.21.0-SNAPSHOT
└─ org.yaml.snakeyaml == 1.33

Dependency Information After the Upgrade

Branch: dependency-upgrade
SHA:    0d785f94ea7e3cb32f26ddc2ab7a6585930a68c6
Maven:  0.21.0-SNAPSHOT
Maven Dependencies Root
os-core-common 0.20.1
(3rd Party) org.yaml.snakeyaml 1.33 
Critical: Found Vulnerable Snake YAML dependency (<2.0)
└─ _Root_
└─ org.opengroup.osdu.os-core-lib-ibm == 0.21.0-SNAPSHOT
└─ org.yaml.snakeyaml == 1.33

Merge request reports