Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • O OS Core Lib Azure
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 8
    • Issues 8
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • Lib
  • cloud
  • azure
  • OS Core Lib Azure
  • Merge requests
  • !198

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 28, 2022
  • Overview 0
  • Commits 1
  • Pipelines 3
  • Changes 1

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:    d385bfe074d62ddd25afe73165e7dc00544f1784
Maven:  0.14.0-SNAPSHOT
Maven Dependencies Root
os-core-common 0.14.0-rc1

Dependency Information After the Upgrade

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