Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • S Storage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 16
    • Merge requests 16
  • 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
  • Storage
  • Merge requests
  • !612

Upgrade First Party Library Dependencies for Release 0.19

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed David Diederich requested to merge dependency-upgrade-3 into master Feb 08, 2023
  • Overview 1
  • Commits 3
  • Pipelines 4
  • Changes 5

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:    6ccebc445eb48ac1a19bc5fdf305017c14df1dee
Maven:  0.20.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.19.0-rc5
core-lib-gcp 0.19.0-rc5
os-core-lib-aws 0.17.0 0.14.0-rc2
obm 0.19.0-rc4
oqm 0.18.0
os-core-common 0.19.0-rc3 0.13.0, 0.18.0-rc3
os-core-lib-ibm 0.17.0-rc4 0.17.0-rc4
osm 0.18.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.14.0 2.8.1, 2.13.2.2
(3rd Party) org.springframework.spring-webflux 5.3.22
(3rd Party) org.springframework.spring-webmvc 5.3.22 5.3.12, 5.3.22

Dependency Information After the Upgrade

Branch: dependency-upgrade-3
SHA:    1fade6d667e0d7beffe7311810be98e5b6ba4a4c
Maven:  0.20.0-SNAPSHOT
Maven Dependencies Root testing/
core-lib-azure 0.19.0
core-lib-gcp 0.19.0
os-core-lib-aws 0.17.0 0.14.0-rc2
obm 0.19.0
oqm 0.19.0
os-core-common 0.19.0 0.13.0, 0.18.0-rc3
os-core-lib-ibm 0.17.0-rc4 0.17.0-rc4
osm 0.19.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.14.0 2.8.1, 2.13.2.2
(3rd Party) org.springframework.spring-webflux 5.3.24
(3rd Party) org.springframework.spring-webmvc 5.3.22 5.3.12, 5.3.22
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: dependency-upgrade-3