Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • P Partition
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • 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
  • Partition
  • Merge requests
  • !202

Upgrade First Party Library Dependencies for Release 0.15

  • Review changes

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

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

Preparing packages...
Preparing packages...
Branch: master
SHA:    88854b20f1b04c5a53bd4293bd946e9ad6ecc330
Maven:  0.15.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.15.0-rc6
core-lib-gcp 0.15.0-rc3, 0.10.0 0.3.25
os-core-lib-aws 0.15.0-SNAPSHOT 0.14.0
obm 0.15.0-rc5
oqm 0.15.0-rc2
os-core-common 0.14.0 0.14.0, 0.3.18
os-core-lib-ibm 0.15.0-rc2 0.14.0
osm 0.15.0-rc5
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.11.4, 2.12.0 2.11.4, 2.9.9.3
(3rd Party) org.apache.logging.log4j.log4j-api 2.17.1 2.13.3, 2.11.1
(3rd Party) org.apache.logging.log4j.log4j-to-slf4j 2.17.1 2.13.3, 2.11.2

Dependency Information After the Upgrade

Preparing packages...
Preparing packages...
Branch: dependency-upgrade
SHA:    b77ecc44669b32f6a958c8c8060cff69aea348f4
Maven:  0.15.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.15.0
core-lib-gcp 0.15.0, 0.10.0 0.3.25
os-core-lib-aws 0.15.0 0.15.0
obm 0.15.0
oqm 0.15.0
os-core-common 0.15.0 0.15.0, 0.3.18
os-core-lib-ibm 0.15.0 0.15.0
osm 0.15.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.13.2, 2.11.4, 2.12.0 2.13.2.2, 2.9.9.3
(3rd Party) org.apache.logging.log4j.log4j-api 2.17.1 2.13.3, 2.11.1
(3rd Party) org.apache.logging.log4j.log4j-to-slf4j 2.17.1 2.13.3, 2.11.2
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: dependency-upgrade