Skip to content

chore: bump oras go to 2.5.0 #1389

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
akashsinghal merged 3 commits into from
Apr 16, 2024
Merged

chore: bump oras go to 2.5.0 #1389

akashsinghal merged 3 commits into from
Apr 16, 2024

Conversation

@akashsinghal
Copy link
Collaborator

@akashsinghal akashsinghal commented Apr 12, 2024

Description

What this PR does / why we need it:

Bumps ORAS-go version to 2.5.0 which adopts GA OCI image spec 1.1.0

Which issue(s) this PR fixes (optional, using fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):

Fixes #1324

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Helm Chart Change (any edit/addition/update that is necessary for changes merged to the main branch)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also list any relevant details for your test configuration

  • Test A
  • Test B

Checklist:

  • Does the affected code have corresponding tests?
  • Are the changes documented, not just with inline documentation, but also with conceptual documentation such as an overview of a new feature, or task-based documentation like a tutorial? Consider if this change should be announced on your project blog.
  • Does this introduce breaking changes that would require an announcement or bumping the major version?
  • Do all new files have appropriate license header?

Post Merge Requirements

  • MAINTAINERS: manually trigger the "Publish Package" workflow after merging any PR that indicates Helm Chart Change

@akashsinghal akashsinghal self-assigned this Apr 12, 2024
@akashsinghal akashsinghal enabled auto-merge (squash) April 12, 2024 17:12
@codecov
Copy link

codecov bot commented Apr 12, 2024 •
edited
Loading

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 65.41%. Comparing base (73ef709) to head (66bf5d0).
Report is 18 commits behind head on staging.

Additional details and impacted files 
@@             Coverage Diff             @@
##           staging    #1389      +/-   ##
===========================================
+ Coverage    65.31%   65.41%   +0.10%     
===========================================
  Files          105      107       +2     
  Lines         5458     5552      +94     
===========================================
+ Hits          3565     3632      +67     
- Misses        1535     1565      +30     
+ Partials       358      355       -3

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@akashsinghal akashsinghal merged commit 7c34a1a into notaryproject:staging Apr 16, 2024
akashsinghal added a commit that referenced this pull request Apr 25, 2024
@akashsinghal
chore: bump oras go to 2.5.0 (#1389)
d17a2d5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@binbin-li binbin-li binbin-li approved these changes

@jimmyraywv jimmyraywv Awaiting requested review from jimmyraywv

@luisdlp luisdlp Awaiting requested review from luisdlp

@susanshi susanshi Awaiting requested review from susanshi

@toddysm toddysm Awaiting requested review from toddysm

Assignees

@akashsinghal akashsinghal

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

Ratify support OCI spec 1.1

2 participants

@akashsinghal @binbin-li