Skip to content
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.

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

Bump golang.org/x/crypto package version to v0.31.0 to fix CVEs. #210

Conversation

blackpiglet
Copy link
Collaborator

@blackpiglet blackpiglet commented Dec 18, 2024

  • Bump golang.org/x/crypto package version to v0.31.0 to fix CVEs
  • Bump Python and GitHub Action versions.

@blackpiglet blackpiglet force-pushed the fix_main_ci_on_release_1.11 branch 2 times, most recently from 69d5be5 to 52852b1 Compare December 18, 2024 10:57
@codecov-commenter
Copy link

codecov-commenter commented Dec 18, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 28.79%. Comparing base (b70331a) to head (056cfea).

Additional details and impacted files
@@              Coverage Diff              @@
##           release-1.11     #210   +/-   ##
=============================================
  Coverage         28.79%   28.79%           
=============================================
  Files                 4        4           
  Lines               566      566           
=============================================
  Hits                163      163           
  Misses              391      391           
  Partials             12       12           

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

@blackpiglet blackpiglet marked this pull request as ready for review December 18, 2024 11:04
@blackpiglet blackpiglet marked this pull request as draft December 18, 2024 11:04
@blackpiglet blackpiglet force-pushed the fix_main_ci_on_release_1.11 branch from 52852b1 to 056cfea Compare December 18, 2024 11:06
@blackpiglet blackpiglet marked this pull request as ready for review December 18, 2024 11:07
@reasonerjt
Copy link
Contributor

Let's create a separate PR for fixing CVE.
As for the git actions.

I'll create a PR when this one is merged:
vmware-tanzu/velero-plugin-for-aws#237

@reasonerjt reasonerjt closed this Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants