Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • U Unit
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 5
    • Issues 5
    • 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
    • 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
  • Unit
  • Merge requests
  • !176

Upgrade Core IBM Library for Release 0.15

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged David Diederich requested to merge core-ibm-upgrade into master Jun 16, 2022
  • Overview 0
  • Commits 1
  • Pipelines 1
  • 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:    f48d3582f5310a72e03a1c1c60735fd6ad672b25
Maven:  0.16.0-SNAPSHOT
Maven Dependencies Root provider/unit-gcp/unit-gae/
core-lib-azure 0.15.0
core-lib-gcp 0.15.0
os-core-lib-aws 0.14.0-rc2
obm 0.15.0
oqm 0.15.0
os-core-common 0.15.0 0.15.0
os-core-lib-ibm 0.15.0
osm 0.15.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.13.2.2, 2.13.2, 2.11.4 2.13.2
Critical: Found Vulnerable Jackson Databind dependency (<2.12.6.1 || >=2.13.0 <2.13.2.1)

Dependency Information After the Upgrade

Branch: core-ibm-upgrade
SHA:    67aec85e33f79fef3edb83fa71efda6d57701403
Maven:  0.16.0-SNAPSHOT
Maven Dependencies Root provider/unit-gcp/unit-gae/
core-lib-azure 0.15.0
core-lib-gcp 0.15.0
os-core-lib-aws 0.14.0-rc2
obm 0.15.0
oqm 0.15.0
os-core-common 0.15.0 0.15.0
os-core-lib-ibm 0.15.2
osm 0.15.0
(3rd Party) com.fasterxml.jackson.core.jackson-databind 2.13.2.2, 2.13.2, 2.11.4 2.13.2
Critical: Found Vulnerable Jackson Databind dependency (<2.12.6.1 || >=2.13.0 <2.13.2.1)
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: core-ibm-upgrade