Skip to content

[release-4.22] OCPBUGS-84431: Bump github.com/moby/spdystream from v0.5.0 to v0.5.1#1529

Open
prdhamdh wants to merge 1 commit into
openshift:release-4.22from
prdhamdh:fix-CVE-2026-35469-4.22
Open

[release-4.22] OCPBUGS-84431: Bump github.com/moby/spdystream from v0.5.0 to v0.5.1#1529
prdhamdh wants to merge 1 commit into
openshift:release-4.22from
prdhamdh:fix-CVE-2026-35469-4.22

Conversation

@prdhamdh
Copy link
Copy Markdown
Contributor

@prdhamdh prdhamdh commented Jun 1, 2026

  • Bump github.com/moby/spdystream from v0.5.0 to v0.5.1 to fix CVE-2026-35469

@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 Jun 1, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@prdhamdh: This pull request references Jira Issue OCPBUGS-84431, 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-84431 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

Details

In response to this:

  • Bump github.com/moby/spdystream from v0.5.0 to v0.5.1 to fix CVE-2026-35469

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.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Jun 1, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Repository: openshift/coderabbit/.coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 27eb0ecc-43e7-4619-83f7-c0f2b64a04ad

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested review from MarSik and jmencak June 1, 2026 07:28
@prdhamdh prdhamdh force-pushed the fix-CVE-2026-35469-4.22 branch from 4c80f05 to cef4cb8 Compare June 1, 2026 09:04
@prdhamdh
Copy link
Copy Markdown
Contributor Author

prdhamdh commented Jun 1, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@prdhamdh: This pull request references Jira Issue OCPBUGS-84431, 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-84431 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

Details

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.

@prdhamdh
Copy link
Copy Markdown
Contributor Author

prdhamdh commented Jun 1, 2026

/jira refresh

@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@prdhamdh: This pull request references Jira Issue OCPBUGS-84431, which is invalid:

  • expected Jira Issue OCPBUGS-84431 to depend on a bug targeting a version in 5.0.0 and in one of the following states: MODIFIED, ON_QA, VERIFIED, 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.

Details

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.

@prdhamdh
Copy link
Copy Markdown
Contributor Author

prdhamdh commented Jun 1, 2026

/retest

1 similar comment
@prdhamdh
Copy link
Copy Markdown
Contributor Author

prdhamdh commented Jun 2, 2026

/retest

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 2, 2026

@prdhamdh: all tests passed!

Full PR test history. Your PR dashboard.

Details

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.

@jmencak
Copy link
Copy Markdown
Contributor

jmencak commented Jun 2, 2026

/lgtm
/approve

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak, prdhamdh

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

The pull request process is described here

Details 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 openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jun 2, 2026
@jmencak
Copy link
Copy Markdown
Contributor

jmencak commented Jun 2, 2026

/label backport-risk-assessed

@openshift-ci openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. 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. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants