-
Notifications
You must be signed in to change notification settings - Fork 891
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 version to 1.22.7 to address security warnings #5529
Conversation
Welcome @yelshall! It looks like this is your first PR to karmada-io/karmada 🎉 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5529 +/- ##
=======================================
Coverage 32.45% 32.45%
=======================================
Files 643 643
Lines 44497 44497
=======================================
+ Hits 14440 14443 +3
+ Misses 28962 28960 -2
+ Partials 1095 1094 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
0e3b4ca
to
946b41c
Compare
Signed-off-by: yelshall <youssuf.elshall@zendesk.com>
946b41c
to
9935ae7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: RainbowMango The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
…5529-upstream-release-1.11 Automated cherry pick of #5529: bump go version to 1.22.7
What type of PR is this?
What this PR does / why we need it:
Bump Golang version to v1.22.7 to address follwoing CVEs:
Which issue(s) this PR fixes:
Fixes #5526
Special notes for your reviewer:
Does this PR introduce a user-facing change?: