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

Update k8s.io/* to v0.31.0 #1474

Closed
wants to merge 1 commit into from
Closed

Update k8s.io/* to v0.31.0 #1474

wants to merge 1 commit into from

Conversation

lou-lan
Copy link
Collaborator

@lou-lan lou-lan commented Sep 3, 2024

No description provided.

@lou-lan lou-lan changed the title Update k8s.io/* to v0.31.0 Update k8s.io/* to v0.31.0 Sep 3, 2024
@lou-lan lou-lan added the release/none should not recoded in new release label Sep 3, 2024
@lou-lan lou-lan force-pushed the upgrade-k8s branch 4 times, most recently from 8ca7a8c to dceede8 Compare September 3, 2024 11:03
Copy link

codecov bot commented Sep 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.37%. Comparing base (81907e9) to head (e768a36).
Report is 20 commits behind head on main.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1474      +/-   ##
==========================================
+ Coverage   81.74%   82.37%   +0.62%     
==========================================
  Files          19       19              
  Lines        2783     2281     -502     
==========================================
- Hits         2275     1879     -396     
+ Misses        397      285     -112     
- Partials      111      117       +6     
Flag Coverage Δ
unittests 82.37% <ø> (+0.62%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

see 17 files with indirect coverage changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release/none should not recoded in new release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants