-
Notifications
You must be signed in to change notification settings - Fork 1.1k
version: bump to 1.25.4 #7183
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
version: bump to 1.25.4 #7183
Conversation
1400c81
to
be0f7e3
Compare
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## release-1.25 #7183 +/- ##
=============================================
Coverage 43.60% 43.60%
=============================================
Files 122 122
Lines 13714 13714
=============================================
Hits 5980 5980
Misses 7087 7087
Partials 647 647 |
I was wondering if we could get #7132 in before merging this PR |
And #7156 as well |
@sohankunkerkar is this ready? |
Signed-off-by: Sohan Kunkerkar <sohank2602@gmail.com>
be0f7e3
to
541cb21
Compare
Yes, it is |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander, sohankunkerkar 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 |
/override ci/prow/e2e-gcp |
@haircommander: Overrode contexts on behalf of haircommander: ci/prow/e2e-gcp In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Is this version released or any ETA on this. |
https://github.com/cri-o/cri-o/releases/tag/v1.25.4 is released! we'll work on getting packaged this week as well |
Thanks for the update. |
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
#6805 (comment)
Special notes for your reviewer:
Does this PR introduce a user-facing change?