-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[v4.0-rhel] Bump c/image v1.38.4, c/storage v5.19.4 #14440
[v4.0-rhel] Bump c/image v1.38.4, c/storage v5.19.4 #14440
Conversation
@TomSweeneyRedHat: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. 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. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: TomSweeneyRedHat 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 |
The branch seems broken:
@Luap99, can you take a look? |
I think you have to backport e5a86d2 |
As the title says. Bump c/image to v1.38.4 and c/storage to v5.19.4. Also backport containers@e5a86d2 for golang ci support. [NO NEW TESTS NEEDED] This partially addresses: https://bugzilla.redhat.com/show_bug.cgi?id=2072452 Signed-off-by: tomsweeneyredhat <[email protected]>
1574468
to
be766d5
Compare
@Luap99 TYVM for the tip, I've included that too. |
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 |
As the title says.
Bump c/image to v1.38.4 and c/storage to v5.19.4.
[NO NEW TESTS NEEDED]
This partially addresses: https://bugzilla.redhat.com/show_bug.cgi?id=2072452
Signed-off-by: tomsweeneyredhat [email protected]
Does this PR introduce a user-facing change?
None