[Release-4.20] OCPBUGS-81959,OCPBUGS-81958,OCPBUGS-81960: Bump github.com/go-jose/go-jose/v4 to v4.1.4 by MrSanketkumar · Pull Request #1295 · openshift/operator-framework-olm

MrSanketkumar · 2026-05-08T11:49:55Z

Summary by CodeRabbit

Chores

Updated cryptographic library dependency to version 4.1.4 across project configurations for improved stability and security.

coderabbitai · 2026-05-08T11:50:01Z

Walkthrough

Two Go module files have their indirect dependency github.com/go-jose/go-jose/v4 bumped from version v4.1.0 to v4.1.4.

Changes

Dependency Updates

Layer / File(s)	Summary
Indirect Dependency Bump `go.mod`, `staging/operator-registry/go.mod`	`github.com/go-jose/go-jose/v4` updated from `v4.1.0` to `v4.1.4` in both module files.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 12

✅ Passed checks (12 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	PR only modifies go.mod files for dependency version updates. No test files are added, modified, or removed. The Stable and Deterministic Test Names check is not applicable to this PR.
Test Structure And Quality	✅ Passed	This PR only modifies go.mod files to bump go-jose/v4 dependency. It contains no test code changes, so the Ginkgo test quality check is not applicable.
Microshift Test Compatibility	✅ Passed	PR only updates go.mod dependencies (go-jose v4.1.0→v4.1.4). No new Ginkgo e2e tests are added, so the MicroShift Test Compatibility check is not applicable.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Custom check not applicable. This PR only updates Go module dependencies (github.com/go-jose/go-jose/v4 from v4.1.0 to v4.1.4) in go.mod files. No new Ginkgo e2e tests are added.
Topology-Aware Scheduling Compatibility	✅ Passed	This PR only updates the go-jose dependency version in go.mod files (v4.1.0→v4.1.4 for CVE-2026-34986). No deployment manifests, operator code, or scheduling constraints were introduced.
Ote Binary Stdout Contract	✅ Passed	PR only updates go.mod dependency versions without code changes. OTE stdout contract requires analyzing source code modifications in process-level functions, which is not applicable here.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	No new Ginkgo e2e tests added. PR only updates go.mod dependencies (github.com/go-jose/go-jose/v4 v4.1.0 to v4.1.4). Check applies only when new Ginkgo tests are added.
Title check	✅ Passed	The title clearly describes the main change: bumping the go-jose/v4 dependency to v4.1.4, which is precisely what both modified files accomplish.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

Create PR with unit tests

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

openshift-ci-robot · 2026-05-08T11:50:03Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, 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-81959 to depend on a bug targeting a version in 4.21.0, 4.21.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.

This pull request references Jira Issue OCPBUGS-81958, 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-81958 to depend on a bug targeting a version in 4.21.0, 4.21.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.

Details

In response to this:

…4986

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-robot · 2026-05-08T11:50:09Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, 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-81959 to depend on a bug targeting a version in 4.21.0, 4.21.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.

This pull request references Jira Issue OCPBUGS-81958, 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-81958 to depend on a bug targeting a version in 4.21.0, 4.21.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.

Details

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.

MrSanketkumar · 2026-05-08T11:50:31Z

@coderabbitai review

coderabbitai · 2026-05-08T11:50:36Z

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

MrSanketkumar · 2026-05-08T11:51:55Z

/jira refresh

openshift-ci-robot · 2026-05-08T11:52:02Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, which is invalid:

expected dependent Jira Issue OCPBUGS-81996 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81958, which is invalid:

expected dependent Jira Issue OCPBUGS-81995 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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:

/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-robot · 2026-05-08T11:54:14Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, which is invalid:

expected dependent Jira Issue OCPBUGS-81996 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81958, which is invalid:

expected dependent Jira Issue OCPBUGS-81995 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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:

Summary by CodeRabbit

Chores

Updated cryptographic library dependency to version 4.1.4 across project configurations for improved stability and security.

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 · 2026-05-08T15:14:48Z

@MrSanketkumar: 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.

MrSanketkumar · 2026-05-11T05:35:22Z

/jira refresh

openshift-ci-robot · 2026-05-11T05:35:39Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, which is invalid:

expected dependent Jira Issue OCPBUGS-81996 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81958, which is invalid:

expected dependent Jira Issue OCPBUGS-81995 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

bandrade · 2026-05-11T17:17:35Z

/label qe-approved
/verified by bandrade

openshift-ci-robot · 2026-05-11T17:17:49Z

@bandrade: This PR has been marked as verified by bandrade.

Details

In response to this:

/label qe-approved
/verified by bandrade

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.

rissh · 2026-05-12T18:52:11Z

/retitle [Release-4.20] OCPBUGS-81959,OCPBUGS-81958,OCPBUGS-81960: Bump github.com/go-jose/go-jose/v4 to v4.1.4

openshift-ci-robot · 2026-05-12T18:52:26Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, which is invalid:

expected dependent Jira Issue OCPBUGS-81996 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81958, which is invalid:

expected dependent Jira Issue OCPBUGS-81995 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81960, 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 dependent Jira Issue OCPBUGS-81997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is New instead

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:

Summary by CodeRabbit

Chores

Updated cryptographic library dependency to version 4.1.4 across project configurations for improved stability and security.

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.

MrSanketkumar · 2026-05-13T05:30:19Z

/jira refresh

openshift-ci-robot · 2026-05-13T05:30:27Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, which is invalid:

expected dependent Jira Issue OCPBUGS-81996 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81958, which is invalid:

expected dependent Jira Issue OCPBUGS-81995 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81960, which is invalid:

expected dependent Jira Issue OCPBUGS-81997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

MrSanketkumar · 2026-05-13T05:31:19Z

/jira refresh

openshift-ci-robot · 2026-05-13T05:31:27Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, which is invalid:

expected dependent Jira Issue OCPBUGS-81996 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81958, which is invalid:

expected dependent Jira Issue OCPBUGS-81995 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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.

This pull request references Jira Issue OCPBUGS-81960, which is invalid:

expected dependent Jira Issue OCPBUGS-81997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is POST instead

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:

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

tmshort · 2026-05-13T13:14:18Z

/lgtm
/approve

I looked at the go.mod/go.sum files. I did not look at the vendor.

rashmigottipati

/lgtm

openshift-ci · 2026-05-13T13:17:00Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: MrSanketkumar, rashmigottipati, tmshort

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:

~~DOWNSTREAM_OWNERS~~ [tmshort]

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

MrSanketkumar · 2026-05-18T06:25:26Z

/jira refresh

openshift-ci-robot · 2026-05-18T06:25:34Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, which is invalid:

expected dependent Jira Issue OCPBUGS-81996 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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.

This pull request references Jira Issue OCPBUGS-81958, which is invalid:

expected dependent Jira Issue OCPBUGS-81995 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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.

This pull request references Jira Issue OCPBUGS-81960, which is invalid:

expected dependent Jira Issue OCPBUGS-81997 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is MODIFIED instead

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.

MrSanketkumar · 2026-05-19T04:13:20Z

/jira refresh

openshift-ci-robot · 2026-05-19T04:13:32Z

@MrSanketkumar: This pull request references Jira Issue OCPBUGS-81959, 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.20.z) matches configured target version for branch (4.20.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-81996 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-81996 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

This pull request references Jira Issue OCPBUGS-81958, 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.20.z) matches configured target version for branch (4.20.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-81995 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-81995 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

This pull request references Jira Issue OCPBUGS-81960, 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.20.z) matches configured target version for branch (4.20.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-81997 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-81997 targets the "4.21.z" version, which is one of the valid target versions: 4.21.0, 4.21.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (ocp-sustaining-admins@redhat.com), skipping review request.

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.

prabhapa · 2026-05-19T05:27:23Z

/label backport-risk-assessed

openshift-ci-robot · 2026-05-19T05:31:14Z

@MrSanketkumar: Jira Issue Verification Checks: Jira Issue OCPBUGS-81959
✔️ 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-81959 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Jira Issue Verification Checks: Jira Issue OCPBUGS-81958
✔️ 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-81958 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Jira Issue Verification Checks: Jira Issue OCPBUGS-81960
✔️ 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-81960 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

Summary by CodeRabbit

Chores

Updated cryptographic library dependency to version 4.1.4 across project configurations for improved stability and security.

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-merge-robot · 2026-05-19T18:47:38Z

Fix included in release 4.20.0-0.nightly-2026-05-19-104829

Bump github.com/go-jose/go-jose/v4@v4.1.0 to v4.1.4 to fix CVE-2026-3…

bfaa566

…4986

MrSanketkumar changed the title ~~[Release-4.20] OCPBUGS-81959,OCPBUGS-81958:Bump github.com/go-jose/go-jose/v4@v4.1.0 to v4.1.4 to fix CVE-2026-3…~~ [Release-4.20] OCPBUGS-81959,OCPBUGS-81958: Bump github.com/go-jose/go-jose/v4 to v4.1.4 May 8, 2026

openshift-ci Bot requested review from dtfranz and rashmigottipati May 8, 2026 11:53

openshift-ci Bot added the qe-approved Signifies that QE has signed off on this PR label May 11, 2026

openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label May 11, 2026

openshift-ci Bot assigned tmshort May 13, 2026

openshift-ci Bot added lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels May 13, 2026

rashmigottipati approved these changes May 13, 2026

View reviewed changes

openshift-ci Bot assigned rashmigottipati May 13, 2026

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 May 19, 2026

openshift-ci Bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label May 19, 2026

openshift-ci Bot assigned bandrade May 19, 2026

openshift-merge-bot Bot merged commit ead54af into openshift:release-4.20 May 19, 2026
13 checks passed

Conversation

MrSanketkumar commented May 8, 2026 • edited by coderabbitai Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary by CodeRabbit

Chores

Uh oh!

coderabbitai Bot commented May 8, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Walkthrough

Changes

Estimated code review effort

Uh oh!

openshift-ci-robot commented May 8, 2026

Uh oh!

openshift-ci-robot commented May 8, 2026

Uh oh!

MrSanketkumar commented May 8, 2026

Uh oh!

coderabbitai Bot commented May 8, 2026

Uh oh!

MrSanketkumar commented May 8, 2026

Uh oh!

openshift-ci-robot commented May 8, 2026

Uh oh!

openshift-ci-robot commented May 8, 2026

Summary by CodeRabbit

Chores

Uh oh!

openshift-ci Bot commented May 8, 2026

Uh oh!

MrSanketkumar commented May 11, 2026

Uh oh!

openshift-ci-robot commented May 11, 2026

Uh oh!

bandrade commented May 11, 2026

Uh oh!

openshift-ci-robot commented May 11, 2026

Uh oh!

rissh commented May 12, 2026

Uh oh!

openshift-ci-robot commented May 12, 2026

Summary by CodeRabbit

Chores

Uh oh!

MrSanketkumar commented May 13, 2026

Uh oh!

openshift-ci-robot commented May 13, 2026

Uh oh!

MrSanketkumar commented May 13, 2026

Uh oh!

openshift-ci-robot commented May 13, 2026

Uh oh!

tmshort commented May 13, 2026

Uh oh!

rashmigottipati left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented May 13, 2026

Uh oh!

MrSanketkumar commented May 18, 2026

Uh oh!

openshift-ci-robot commented May 18, 2026

Uh oh!

MrSanketkumar commented May 19, 2026

Uh oh!

openshift-ci-robot commented May 19, 2026

Uh oh!

prabhapa commented May 19, 2026

Uh oh!

Uh oh!

openshift-ci-robot commented May 19, 2026

Summary by CodeRabbit

Chores

Uh oh!

openshift-merge-robot commented May 19, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

MrSanketkumar commented May 8, 2026 •

edited by coderabbitai Bot

Loading

coderabbitai Bot commented May 8, 2026 •

edited

Loading