Skip to content

Full Upgrade of First Party Library Dependencies for Release 0.25

David Diederich requested to merge dependency-upgrade into master

This generated MR upgrades the first party libraries (other OSDU libraries) to utilize the latest release. The intent is to try to fully upgrade all dependent libraries to see if the latest code will work. It is expected that these will often fail, since the upgrades were previously rejected for failing pipelines and have not been directly addressed yet. This 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.

This MR may co-exist with a separate, smaller upgrade MR. If both pass, this one should be used instead.

Dependency Information Before the Upgrade

Branch: master
SHA:    78ff9a023d1c473fb4e6dc795bf2333e520f60df
Maven:  0.26.0-SNAPSHOT
Maven Dependencies Root testing/
apd-core 0.24.0-rc1
core-lib-azure 0.24.0 0.24.0
core-lib-gc 0.24.0
core-plus-common-lib 0.24.0-rc2
os-core-lib-aws 0.25.0-rc2 0.25.0-rc2
obm 0.24.0
oqm 0.24.0
os-core-common 0.25.0-rc2 0.24.0
os-core-lib-ibm 0.24.0 0.24.0
os-obm-core 0.25.0-rc1
os-oqm-core 0.25.0-rc1
os-osm-core 0.25.0-rc2
osm 0.24.0

Dependency Information After the Upgrade

Branch: dependency-upgrade
SHA:    84203ee9fbe2fb3a08035328a55dfa2fa13d541e
Maven:  0.26.0-SNAPSHOT
Maven Dependencies testing/ Root
core-lib-azure 0.25.0
os-core-lib-aws 0.25.0
os-core-common 0.25.0 0.25.0
os-core-lib-ibm 0.25.0

Merge request reports