Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • P Partition
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 5
    • Merge requests 5
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • 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 SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Partition
  • Merge requests
  • !159

Upgrade First Party Library Dependencies for Release 0.14

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged David Diederich requested to merge dependency-upgrade into master Mar 29, 2022
  • Overview 0
  • Commits 3
  • Pipelines 3
  • 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

Branch: master
SHA:    0bfacd70af04eafad63846ec27a441d4ce02ae98
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.14.0-rc2
core-lib-gcp 0.14.0-rc2, 0.10.0 0.3.25
os-core-lib-aws 0.14.0-SNAPSHOT 0.13.0
obm 0.13.1-SNAPSHOT
oqm 0.13.0-SNAPSHOT
os-core-common 0.13.0 0.13.0, 0.3.18
os-core-lib-ibm 0.13.0 0.13.0
osm 0.13.0-SNAPSHOT
(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

Branch: dependency-upgrade
SHA:    7da4f51f513d0b290b9cf342315d8ed05d61f306
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.14.0
core-lib-gcp 0.14.0, 0.10.0 0.3.25
os-core-lib-aws 0.14.0 0.14.0
obm 0.14.0
oqm 0.14.0
os-core-common 0.14.0 0.14.0, 0.3.18
os-core-lib-ibm 0.14.0 0.14.0
osm 0.14.0
(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
Reviewers
Request review from
Time tracking
Source branch: dependency-upgrade