Skip to content

[release-4.20] OCPBUGS-81942: Bump go-jose/go-jose/v4@v4.1.4 - #611

Open
katekeiroz-dev wants to merge 2 commits into
openshift:release-4.20from
katekeiroz-dev:CVE-2026-34986-4.20
Open

[release-4.20] OCPBUGS-81942: Bump go-jose/go-jose/v4@v4.1.4#611
katekeiroz-dev wants to merge 2 commits into
openshift:release-4.20from
katekeiroz-dev:CVE-2026-34986-4.20

Conversation

@katekeiroz-dev

Copy link
Copy Markdown

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 Jun 3, 2026
@openshift-ci-robot

Copy link
Copy Markdown

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-81942, 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-81942 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:

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

coderabbitai Bot commented Jun 3, 2026

Copy link
Copy Markdown

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: Pro Plus

Run ID: c2ccaa6d-d699-4bcb-a4c3-c9fb516d5f63

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.

@katekeiroz-dev

Copy link
Copy Markdown
Author

/ok-to-test

@openshift-ci openshift-ci Bot added the ok-to-test Indicates a non-member PR verified by an org member that is safe to test. label Jun 3, 2026
@openshift-ci
openshift-ci Bot requested review from damdo and theobarberbany June 3, 2026 11:03
@openshift-ci

openshift-ci Bot commented Jun 3, 2026

Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign joelspeed for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@katekeiroz-dev katekeiroz-dev changed the title [release-4.20] OCPBUGS-81942: Bump go-jose/go-jose/v4@v4.1.4 [release-4.21] OCPBUGS-81942: Bump go-jose/go-jose/v4@v4.1.4 Jul 22, 2026
@katekeiroz-dev
katekeiroz-dev changed the base branch from release-4.20 to release-4.21 July 22, 2026 13:36
@openshift-ci-robot

Copy link
Copy Markdown

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-81942, which is invalid:

  • expected the vulnerability to target either version "4.21." or "openshift-4.21.", but it targets "4.20.z" instead
  • expected dependent Jira Issue OCPBUGS-81976 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED instead
  • expected dependent Jira Issue OCPBUGS-81976 to target a version in 4.22.0, but it targets "4.21.z" 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:

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 added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 22, 2026
@katekeiroz-dev
katekeiroz-dev changed the base branch from release-4.21 to release-4.20 July 22, 2026 13:53
@openshift-ci-robot

Copy link
Copy Markdown

@katekeiroz-dev: This pull request references Jira Issue OCPBUGS-81942, which is invalid:

  • expected dependent Jira Issue OCPBUGS-81976 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED 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:

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.

@katekeiroz-dev

Copy link
Copy Markdown
Author

/retest

@openshift-ci openshift-ci Bot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 22, 2026
@damdo

damdo commented Jul 23, 2026

Copy link
Copy Markdown
Member

@katekeiroz-dev this is not of the necessary format. It should be in 2 commits (one UPSTREAM: UPSTREAMPRNUMBER: zzzz one UPSTREAM: <drop>: vendor

see: #606

@damdo damdo changed the title [release-4.21] OCPBUGS-81942: Bump go-jose/go-jose/v4@v4.1.4 [release-4.20] OCPBUGS-81942: Bump go-jose/go-jose/v4@v4.1.4 Jul 23, 2026
Signed-off-by: Kate Barreiros <kbarreir@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Kate Barreiros <kbarreir@redhat.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@openshift-ci

openshift-ci Bot commented Aug 12, 2026

Copy link
Copy Markdown

@katekeiroz-dev: The following tests 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/e2e-aws-serial-2of2 82d2386 link true /test e2e-aws-serial-2of2
ci/prow/e2e-aws-ovn 82d2386 link true /test e2e-aws-ovn
ci/prow/e2e-aws-capi-techpreview 82d2386 link false /test e2e-aws-capi-techpreview
ci/prow/e2e-hypershift 82d2386 link true /test e2e-hypershift
ci/prow/okd-scos-images 82d2386 link true /test okd-scos-images
ci/prow/e2e-aws-serial-1of2 82d2386 link true /test e2e-aws-serial-1of2
ci/prow/unit ec745e5 link true /test unit

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

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. ok-to-test Indicates a non-member PR verified by an org member that is safe to test.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants