Skip to content

OCPBUGS-61446: Update x/crypto to v0.31.0 #335

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.

Sign up for GitHub

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

Jump to bottom
Merged
merged 1 commit into from
Oct 6, 2025
Merged

OCPBUGS-61446: Update x/crypto to v0.31.0 #335

merged 1 commit into from
Oct 6, 2025
+14,243 −6,290

Conversation

dusk125
Copy link

@dusk125 dusk125 commented Sep 23, 2025

No description provided.

@openshift-ci-robot openshift-ci-robot added jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 23, 2025
@openshift-ci-robot
Copy link

@dusk125: This pull request references Jira Issue OCPBUGS-61446, which is invalid:

  • release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
  • expected Jira Issue OCPBUGS-61446 to depend on a bug targeting a version in 4.17.0, 4.17.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from deads2k September 23, 2025 13:52
@dusk125
Copy link
Author

dusk125 commented Sep 23, 2025

/retest

1 similar comment
@dusk125
Copy link
Author

dusk125 commented Sep 24, 2025

/retest

@everettraven
Copy link

/lgtm

@ibihim
Copy link

ibihim commented Sep 24, 2025

/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 24, 2025
@dusk125
Copy link
Author

dusk125 commented Sep 24, 2025

/retest

@sjenning sjenning added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 24, 2025
@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Sep 24, 2025

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: dusk125, everettraven, ibihim

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sjenning sjenning added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Sep 24, 2025
@dusk125
Copy link
Author

dusk125 commented Sep 26, 2025

/retest

@dusk125
Copy link
Author

dusk125 commented Sep 30, 2025

/verified bypass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 30, 2025
@openshift-ci-robot
Copy link

@dusk125: The verified label has been added.

In response to this:

/verified bypass

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 openshift-eng/jira-lifecycle-plugin repository.

@dusk125
Copy link
Author

dusk125 commented Oct 1, 2025

/retest

1 similar comment
@dusk125
Copy link
Author

dusk125 commented Oct 1, 2025

/retest

@dusk125
Copy link
Author

dusk125 commented Oct 2, 2025

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Oct 2, 2025
@openshift-ci-robot
Copy link

@dusk125: This pull request references Jira Issue OCPBUGS-61446, which is valid. The bug has been moved to the POST state.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.16.z) matches configured target version for branch (4.16.z)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note text is set and does not match the template
  • dependent bug Jira Issue OCPBUGS-61445 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
  • dependent Jira Issue OCPBUGS-61445 targets the "4.17.z" version, which is one of the valid target versions: 4.17.0, 4.17.z
  • bug has dependents

Requesting review from QA contact:
/cc @xiaojiey

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from xiaojiey October 2, 2025 12:55
@dusk125
Copy link
Author

dusk125 commented Oct 2, 2025

/retest

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 30f8012 and 2 for PR HEAD d76ae9a in total

@dusk125
Copy link
Author

dusk125 commented Oct 3, 2025

Attempting to fix the e2e-component failure by backporting this fix: #338

@dusk125
Copy link
Author

dusk125 commented Oct 6, 2025

/retest

@openshift-ci OpenShift CI
Copy link

openshift-ci bot commented Oct 6, 2025

@dusk125: all tests passed!

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

@openshift-merge-bot openshift-merge-bot bot merged commit 565f7ed into openshift:release-4.16 Oct 6, 2025
8 checks passed
@openshift-ci-robot
Copy link

@dusk125: Jira Issue Verification Checks: Jira Issue OCPBUGS-61446
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-61446 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

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 openshift-eng/jira-lifecycle-plugin repository.

@dusk125 dusk125 deleted the 4.16-cve-fix branch October 6, 2025 17:04
@openshift-merge-robot
Copy link

Fix included in accepted release 4.16.0-0.nightly-2025-10-07-073920

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@deads2k deads2k Awaiting requested review from deads2k

@xiaojiey xiaojiey Awaiting requested review from xiaojiey

Assignees

@everettraven everettraven

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/severity-important Referenced Jira bug's severity is important for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

6 participants

@dusk125 @openshift-ci-robot @everettraven @ibihim @openshift-merge-robot @sjenning