koordinator
koordinator copied to clipboard
chores: bump golang.org/x/net version 0.12.0 to 0.17.0
Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?
fixes https://github.com/advisories/GHSA-qppj-fm5r-hxr3
Ⅲ. Describe how to verify it
Ⅳ. Special notes for reviews
V. Checklist
- [x] I have written necessary docs and comments
- [x] I have added necessary unit tests and integration tests
- [x] All checks passed in
make test
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 67.00%. Comparing base (
c70f410
) to head (4ba4e71
). Report is 90 commits behind head on main.
Additional details and impacted files
@@ Coverage Diff @@
## main #1743 +/- ##
==========================================
- Coverage 67.03% 67.00% -0.03%
==========================================
Files 407 407
Lines 45557 45557
==========================================
- Hits 30538 30525 -13
- Misses 12796 12804 +8
- Partials 2223 2228 +5
Flag | Coverage Δ | |
---|---|---|
unittests | 67.00% <ø> (-0.03%) |
:arrow_down: |
Flags with carried forward coverage won't be shown. Click here to find out more.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
New changes are detected. LGTM label has been removed.
New changes are detected. LGTM label has been removed.
@jasonliu747 addressed comments, please review :)
/assign @hormes
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jasonliu747 To complete the pull request process, please ask for approval from hormes after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve
in a comment
Approvers can cancel approval by writing /approve cancel
in a comment
This issue has been automatically marked as stale because it has not had recent activity. This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied, the issue is closed You can: - Mark this issue or PR as fresh with
/remove-lifecycle stale
- Close this issue or PR with
/close
Thank you for your contributions.
This issue has been automatically closed because it has not had recent activity. This bot triages issues and PRs according to the following rules:
- After 90d of inactivity,
lifecycle/stale
is applied - After 30d of inactivity since
lifecycle/stale
was applied, the issue is closed You can: - Reopen this PR with
/reopen
Thank you for your contributions.