builder icon indicating copy to clipboard operation
builder copied to clipboard

updating golang.org/x/crypto to v0.17.0

Open ayushsatyam146 opened this issue 1 year ago • 8 comments

ayushsatyam146 avatar May 06 '24 09:05 ayushsatyam146

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ayushsatyam146 Once this PR has been reviewed and has the lgtm label, please assign adambkaplan for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment Approvers can cancel approval by writing /approve cancel in a comment

openshift-ci[bot] avatar May 06 '24 09:05 openshift-ci[bot]

@ayushsatyam146: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/security 135a485b3bb2fdab7c8a0cc9a658eab5614b2398 link false /test security

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

openshift-ci[bot] avatar May 06 '24 11:05 openshift-ci[bot]

/cherrypick release-4.14

ayushsatyam146 avatar May 06 '24 11:05 ayushsatyam146

@ayushsatyam146: once the present PR merges, I will cherry-pick it on top of release-4.14 in a new PR and assign it to you.

In response to this:

/cherrypick release-4.14

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.

/cherrypick release-4.13

ayushsatyam146 avatar May 06 '24 11:05 ayushsatyam146

@ayushsatyam146: once the present PR merges, I will cherry-pick it on top of release-4.13 in a new PR and assign it to you.

In response to this:

/cherrypick release-4.13

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.

/cherrypick release-4.12

ayushsatyam146 avatar May 06 '24 11:05 ayushsatyam146

@ayushsatyam146: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you.

In response to this:

/cherrypick release-4.12

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.

@ayushsatyam146 for CVE fixes in OpenShift, please do the following:

  1. Use master as the base branch for your changes
  2. Open the pull request against the master branch first.
  3. Ensure your commit message AND pull request reference the JIRA issue first (ex: OCPBUGS-25495)
  4. Ensure your pull request has a full, complete description. We have automation that generates pre-release notes from pull request descriptions.

adambkaplan avatar May 07 '24 13:05 adambkaplan

This is a "textbook" example of what OpenShift is looking for: https://github.com/openshift/builder/pull/386

adambkaplan avatar May 07 '24 13:05 adambkaplan