Skip to content

DFBUGS-6250:[release-4.14] godeps: update go-jose version - #785

Open
iamniting wants to merge 2 commits into
red-hat-storage:release-4.14from
iamniting:CVE-2026-34986-4.14
Open

DFBUGS-6250:[release-4.14] godeps: update go-jose version#785
iamniting wants to merge 2 commits into
red-hat-storage:release-4.14from
iamniting:CVE-2026-34986-4.14

Conversation

@iamniting

Copy link
Copy Markdown
Member

Signed-off-by: Nitin Goyal nigoyal@redhat.com

@openshift-ci

openshift-ci Bot commented May 5, 2026

Copy link
Copy Markdown
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: iamniting

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 May 5, 2026
@iamniting iamniting changed the title [release-4.14] godeps: update go-jose version DFBUGS-6250:[release-4.14] godeps: update go-jose version May 5, 2026
@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 the referenced jira bug is invalid for the branch this PR is targeting labels May 5, 2026
@openshift-ci-robot

openshift-ci-robot commented May 5, 2026

Copy link
Copy Markdown

@iamniting: This pull request references [Jira Issue DFBUGS-6250](https://redhat.atlassian.net/browse/DFBUGS-6250), which is invalid:

  • expected the vulnerability to target the "odf-4.14.29" version, but no target version was set

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:

Signed-off-by: Nitin Goyal nigoyal@redhat.com

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.

iamniting added 2 commits May 18, 2026 14:21
Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
Signed-off-by: Nitin Goyal <nigoyal@redhat.com>
@iamniting
iamniting force-pushed the CVE-2026-34986-4.14 branch from 162d98f to a952e97 Compare May 18, 2026 08:51
@openshift-ci

openshift-ci Bot commented May 18, 2026

Copy link
Copy Markdown
Contributor

@iamniting: 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/odf-operator-e2e-aws a952e97 link true /test odf-operator-e2e-aws

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.

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. jira/invalid-bug Indicates that the 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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants