Upgrade First Party Library Dependencies for Release 0.21
This generated 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: 4b2ff3991743167c4e91aa86e569c33af70ff67c
Maven: 0.22.0-SNAPSHOT
Maven Dependencies | Root | testing/ |
---|---|---|
core-lib-azure | 0.14.0-rc2 | 0.6.1 |
core-lib-gcp | 0.19.0-rc3 | |
os-core-lib-aws | 0.21.0-rc5 | 0.21.0-rc5 |
obm | 0.18.0 | |
oqm | 0.18.0 | |
os-core-common | 0.19.0-rc6 | 0.19.0-rc6 |
os-core-lib-ibm | 0.16.0-rc1 | 0.15.2 |
osm | 0.18.0 | |
(3rd Party) net.minidev.json-smart | 2.4.7 | 2.3 |
(3rd Party) org.apache.logging.log4j.log4j-api | 2.17.1 | 2.13.3 |
(3rd Party) org.apache.logging.log4j.log4j-core | 2.17.1 | 2.13.3 |
(3rd Party) org.apache.logging.log4j.log4j-jul | 2.17.1 | 2.13.3 |
(3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.17.1 | 2.13.3 |
(3rd Party) org.springframework.spring-webflux | 5.3.12 | |
(3rd Party) org.yaml.snakeyaml | 1.30, 2.0, 1.33, 1.26 | 2.0 |
Critical: Found Vulnerable Snake YAML dependency (<2.0)
└─ _Root_
├─ org.springdoc.springdoc-openapi-ui == 1.6.14
│ └─ org.springdoc.springdoc-openapi-webmvc-core == 1.6.14
│ └─ org.springdoc.springdoc-openapi-common == 1.6.14
│ └─ org.springframework.boot.spring-boot-autoconfigure == 2.7.7
│ └─ io.swagger.core.v3.swagger-core == 2.2.7
│ └─ org.yaml.snakeyaml == 1.30
├─ org.opengroup.osdu.os-schema-gc == 0.22.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-schema-core == 0.22.0-SNAPSHOT
│ └─ org.yaml.snakeyaml == 1.33
├─ org.opengroup.osdu.os-schema-ibm == 0.22.0-SNAPSHOT
│ └─ org.opengroup.osdu.os-schema-core == 0.22.0-SNAPSHOT
│ └─ org.yaml.snakeyaml == 1.33
└─ org.opengroup.osdu.os-schema-azure == 0.22.0-SNAPSHOT
└─ org.opengroup.osdu.os-schema-core == 0.22.0-SNAPSHOT
└─ org.yaml.snakeyaml == 1.26
Critical: Found Vulnerable Spring WebFlux dependency (<5.2.20 || >=5.3.0 <5.3.18)
└─ _Root_
└─ org.opengroup.osdu.os-schema-azure == 0.22.0-SNAPSHOT
└─ org.springframework.boot.spring-boot-starter-webflux == 2.6.6
└─ org.springframework.spring-webflux == 5.3.12
Dependency Information After the Upgrade
Branch: dependency-upgrade
SHA: 817299c4b5d51e0e0bda89896914dc934be4e3ef
Maven: 0.22.0-SNAPSHOT
Maven Dependencies | testing/ | Root |
---|---|---|
core-lib-azure | 0.6.1 | |
os-core-lib-aws | 0.21.0 | 0.21.0 |
os-core-common | 0.19.0-rc6 | 0.19.0-rc6 |
os-core-lib-ibm | 0.15.2 | |
(3rd Party) net.minidev.json-smart | 2.3 | 2.4.7 |
(3rd Party) org.apache.logging.log4j.log4j-api | 2.13.3 | 2.17.1 |
(3rd Party) org.apache.logging.log4j.log4j-core | 2.13.3 | |
(3rd Party) org.apache.logging.log4j.log4j-jul | 2.13.3 | |
(3rd Party) org.apache.logging.log4j.log4j-slf4j-impl | 2.13.3 | |
(3rd Party) org.yaml.snakeyaml | 2.0 | 1.30, 2.0 |
Critical: Found Vulnerable Snake YAML dependency (<2.0)
└─ _Root_
└─ org.springdoc.springdoc-openapi-ui == 1.6.14
└─ org.springdoc.springdoc-openapi-webmvc-core == 1.6.14
└─ org.springdoc.springdoc-openapi-common == 1.6.14
└─ org.springframework.boot.spring-boot-autoconfigure == 2.7.7
└─ io.swagger.core.v3.swagger-core == 2.2.7
└─ org.yaml.snakeyaml == 1.30
Merge request reports
Activity
changed milestone to %M18 - Release 0.21
added MRDependencies Upgrade no-detached-pipeline labels
@Yauhen_Shaliou @Rustam_Lotsmanenko - could you help ? GC is not compiling
cc: @Yurii_Ruban
added 5 commits
-
d3e07dea...0d2dad1c - 4 commits from branch
master
- b7b36eed - Merge branch 'master' into dependency-upgrade
-
d3e07dea...0d2dad1c - 4 commits from branch
added 2 commits
@ydzeng - I think the AWS bootstrap failure is unrelated- can you confirm if we can proceed with this upgrade?
@Srinivasan_Narayanan @deepapathak - azure test is failing can you help confirm.
Hello @chad,
Changes are not related to azure, so we can proceed.
mentioned in commit f03d5ba7
mentioned in merge request !502 (merged)