Skip to content

DFBUGS-6264: build: update dependencies for ODF 4.17 - #337

Open
subhamkrai wants to merge 1 commit into
red-hat-storage:release-4.17from
subhamkrai:fix/security-cves-release-4.17
Open

DFBUGS-6264: build: update dependencies for ODF 4.17#337
subhamkrai wants to merge 1 commit into
red-hat-storage:release-4.17from
subhamkrai:fix/security-cves-release-4.17

Conversation

@subhamkrai

@subhamkrai subhamkrai commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

@openshift-ci

openshift-ci Bot commented Jun 3, 2026

Copy link
Copy Markdown

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci

openshift-ci Bot commented Jun 3, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: subhamkrai

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 label Jun 3, 2026
@subhamkrai
subhamkrai marked this pull request as ready for review June 9, 2026 10:18
Bump github.com/go-jose/go-jose/v4 from v4.1.3 to v4.1.4.

Fixed Jira:
- https://redhat.atlassian.net/browse/DFBUGS-6264
- https://redhat.atlassian.net/browse/DFBUGS-4503
- https://redhat.atlassian.net/browse/DFBUGS-5476
- https://redhat.atlassian.net/browse/DFBUGS-5144

Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: subhamkrai <srai@redhat.com>
@subhamkrai
subhamkrai force-pushed the fix/security-cves-release-4.17 branch from 5e47fa9 to a1010fa Compare June 11, 2026 10:31
@subhamkrai subhamkrai changed the title build: update dependencies for ODF 4.17 DFBUGS-6264: build: update dependencies for ODF 4.17 Jul 6, 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 Jul 6, 2026
@openshift-ci-robot

openshift-ci-robot commented Jul 6, 2026

Copy link
Copy Markdown

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

  • expected the vulnerability to target the "odf-4.17.28" 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.

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

Details

In response to this:

Bump github.com/go-jose/go-jose/v4 from v4.1.3 to v4.1.4.

Fixed Jira:

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.

@subhamkrai

Copy link
Copy Markdown
Contributor Author

/jira refresh

@openshift-ci-robot

openshift-ci-robot commented Jul 21, 2026

Copy link
Copy Markdown

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

  • expected the vulnerability to target the "odf-4.17.28" 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:

/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.

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

Labels

approved 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