Skip to content
New issue

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

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

Already on GitHub? # to your account

Bump to containerd v2.0.3/runc v1.2.5 #11863

Merged
merged 1 commit into from
Mar 3, 2025

Conversation

brandond
Copy link
Member

Proposed Changes

Bump to containerd v2.0.3/runc v1.2.5

Types of Changes

version bump

Verification

Check versions
See linked issue

Testing

Linked Issues

User-Facing Change

Further Comments

@brandond brandond requested a review from a team as a code owner February 28, 2025 21:54
@brandond brandond force-pushed the bump-containerd-runc branch 2 times, most recently from b1ef758 to 9059bf9 Compare March 1, 2025 05:01
Copy link

codecov bot commented Mar 1, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.94%. Comparing base (8aa543e) to head (2b8344f).
Report is 2 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #11863      +/-   ##
==========================================
- Coverage   45.72%   44.94%   -0.79%     
==========================================
  Files         190      190              
  Lines       19094    19094              
==========================================
- Hits         8731     8581     -150     
- Misses       9081     9272     +191     
+ Partials     1282     1241      -41     
Flag Coverage Δ
e2etests 35.87% <ø> (+1.15%) ⬆️
inttests 35.36% <ø> (+0.08%) ⬆️
unittests 16.81% <ø> (ø)

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

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

Signed-off-by: Brad Davidson <brad.davidson@rancher.com>
@brandond brandond force-pushed the bump-containerd-runc branch from 9059bf9 to 2b8344f Compare March 1, 2025 05:37
@farazkhawaja
Copy link

Hi, would this change resolve the linked issue?

@brandond
Copy link
Member Author

brandond commented Mar 3, 2025

@farazkhawaja yes, thats why it's linked.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants