Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S Storage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe Software
  • Platform
  • System
  • Storage
  • Merge requests
  • !432

Upgrade First Party Library Dependencies for Release 0.15

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed David Diederich requested to merge dependency-upgrade into master Jun 06, 2022
  • Overview 1
  • Commits 7
  • Pipelines 7
  • Changes 5

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:    2daa9f91b8ea3554298a4568e9662057ce8f9979
Maven:  0.15.0-SNAPSHOT
Maven Dependencies Root provider/storage-aws/src/main/ComplianceTrigger/ComplianceTriggerFunction/ComplianceTriggerFunction/ testing/
core-lib-azure 0.14.0-rc5
core-lib-gcp 0.15.0-rc3, 0.13.0
os-core-lib-aws 0.14.0-rc2, 0.3.8 0.14.0-rc2 0.14.0-rc2, 0.3.8
obm 0.15.0-rc5
oqm 0.15.0-rc2
os-core-common 0.15.0-SNAPSHOT 0.13.0 0.13.0
os-core-lib-ibm 0.15.0-rc2 0.13.0
osm 0.15.0-rc5
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.13.2.2 2.6.7.2 2.8.1, 2.13.2.2
(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 2.17.1
(3rd Party) org.apache.logging.log4j.log4j-to-slf4j 2.17.1 2.13.3 2.17.1

Dependency Information After the Upgrade

Branch: dependency-upgrade
SHA:    b3c7621d5d93a074c19aff2ca557d282a8d380d7
Maven:  0.15.0-SNAPSHOT
Maven Dependencies Root provider/storage-aws/src/main/ComplianceTrigger/ComplianceTriggerFunction/ComplianceTriggerFunction/ testing/
core-lib-azure 0.14.0-rc5
core-lib-gcp 0.15.0, 0.13.0
os-core-lib-aws 0.14.0-rc2, 0.3.8 0.14.0-rc2 0.14.0-rc2, 0.3.8
obm 0.15.0
oqm 0.15.0
os-core-common 0.15.0 0.13.0 0.13.0
os-core-lib-ibm 0.15.1 0.13.0
osm 0.15.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.13.2.2 2.6.7.2 2.8.1, 2.13.2.2
(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 2.17.1
(3rd Party) org.apache.logging.log4j.log4j-to-slf4j 2.17.1 2.13.3 2.17.1
Edited Jun 09, 2022 by David Diederich
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: dependency-upgrade