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
  • !393

Upgrade First Party Library Dependencies for Release 0.14

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed David Diederich requested to merge dependency-upgrade into master Mar 29, 2022
  • Overview 1
  • Commits 2
  • Pipelines 2
  • Changes 13

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:    78528a84830e9bdec9fac22e14df1884f9dba976
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root provider/storage-aws/src/main/ComplianceTrigger/ComplianceTriggerFunction/ComplianceTriggerFunction/ testing/
core-lib-azure 0.14.0-rc3
core-lib-gcp 0.14.0-rc2, 0.13.0
os-core-lib-aws 0.13.0, 0.3.8 0.10.0 0.10.0, 0.3.7
obm 0.13.1-SNAPSHOT
oqm 0.13.0-SNAPSHOT
os-core-common 0.14.0-rc6, 0.14.0-rc8 0.13.0 0.13.0
os-core-lib-ibm 0.13.0 0.13.0
osm 0.13.0-SNAPSHOT
(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:    84cea0aed4d76c3fc55e7155d72c72410b1f7171
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root provider/storage-aws/src/main/ComplianceTrigger/ComplianceTriggerFunction/ComplianceTriggerFunction/ testing/
core-lib-azure 0.14.0
core-lib-gcp 0.14.0
os-core-lib-aws 0.14.0, 0.3.8 0.10.0 0.10.0, 0.3.7
obm 0.14.0
oqm 0.14.0
os-core-common 0.14.0 0.14.0 0.14.0
os-core-lib-ibm 0.14.0 0.14.0
osm 0.14.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 2.17.1
(3rd Party) org.apache.logging.log4j.log4j-to-slf4j 2.17.1 2.13.3 2.17.1
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: dependency-upgrade