Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • C CRS Catalog
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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 SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Reference and Helper ServicesReference and Helper Services
  • CRS Catalog
  • Merge requests
  • !128

Upgrade First Party Library Dependencies for Release 0.14

  • Review changes

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

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:    dabba6c7702bbb7d60cdef1fbce1b7c38f9d3aaa
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root
core-lib-azure 0.14.0-rc2
os-core-common 0.13.0
os-core-lib-ibm 0.13.0

Dependency Information After the Upgrade

Branch: dependency-upgrade
SHA:    f79996ebc667ad7a7b30a3523e3ba877f5a27b4c
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root
core-lib-azure 0.14.0
os-core-common 0.14.0
os-core-lib-ibm 0.14.0
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: dependency-upgrade