OCPBUGS-51226,OCPBUGS-51228,OCPBUGS-51246: (vendor) pin go-jose/v4@v4.0.5 by anik120 · Pull Request #998 · openshift/operator-framework-olm

anik120 · 2025-05-06T19:06:33Z

Upstream-repository: operator-lifecycle-manager
Upstream-commit: dfd0b2bea85038d3c0d65348bc812d297f16b8d2

Upstream-repository: operator-lifecycle-manager Upstream-commit: dfd0b2bea85038d3c0d65348bc812d297f16b8d2

openshift-ci-robot · 2025-05-06T19:06:43Z

@anik120: This pull request references Jira Issue OCPBUGS-51226, 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.

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-51228, 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-51228 to depend on a bug targeting a version in 4.18.0, 4.18.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-51246, 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-51246 to depend on a bug targeting a version in 4.18.0, 4.18.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:

Upstream-repository: operator-lifecycle-manager
Upstream-commit: dfd0b2bea85038d3c0d65348bc812d297f16b8d2

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.

anik120 · 2025-05-06T19:32:17Z

/jira refresh

openshift-ci-robot · 2025-05-06T19:32:26Z

@anik120: This pull request references Jira Issue OCPBUGS-51226, 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.

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-51228, 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.

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-51246, 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.17.z) matches configured target version for branch (4.17.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-51245 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-51245 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@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.

anik120 · 2025-05-06T19:42:45Z

/jira refresh

openshift-ci-robot · 2025-05-06T19:42:54Z

@anik120: This pull request references Jira Issue OCPBUGS-51226, 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.

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-51228, 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.17.z) matches configured target version for branch (4.17.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-51227 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-51227 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
bug has dependents

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

This pull request references Jira Issue OCPBUGS-51246, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.17.z) matches configured target version for branch (4.17.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-51245 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-51245 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@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.

anik120 · 2025-05-06T19:44:16Z

/jira refresh

openshift-ci-robot · 2025-05-06T19:44:30Z

@anik120: This pull request references Jira Issue OCPBUGS-51226, 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.17.z) matches configured target version for branch (4.17.z)
bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-51225 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-51225 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
bug has dependents

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

This pull request references Jira Issue OCPBUGS-51228, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.17.z) matches configured target version for branch (4.17.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-51227 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-51227 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
bug has dependents

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

This pull request references Jira Issue OCPBUGS-51246, which is valid.

7 validation(s) were run on this bug

bug is open, matching expected state (open)
bug target version (4.17.z) matches configured target version for branch (4.17.z)
bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
release note type set to "Release Note Not Required"
dependent bug Jira Issue OCPBUGS-51245 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-51245 targets the "4.18.z" version, which is one of the valid target versions: 4.18.0, 4.18.z
bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (bandrade@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.

bandrade · 2025-05-06T19:50:06Z

/label cherry-pick-approved

perdasilva · 2025-05-07T11:13:21Z

/retest

camilamacedo86

/lgtm

openshift-ci · 2025-05-07T12:41:09Z

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: anik120, camilamacedo86

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~~ [anik120]

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

oceanc80 · 2025-05-07T15:37:40Z

/label backport-risk-assessed

openshift-ci-robot · 2025-05-07T16:24:28Z

/retest-required

Remaining retests: 0 against base HEAD d3b1715 and 2 for PR HEAD f71c731 in total

openshift-ci · 2025-05-07T20:02:27Z

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

openshift-ci-robot · 2025-05-07T20:05:24Z

@anik120: Jira Issue OCPBUGS-51226: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#998

Jira Issue OCPBUGS-51226 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-51228: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#998

Jira Issue OCPBUGS-51228 has been moved to the MODIFIED state.

Jira Issue OCPBUGS-51246: All pull requests linked via external trackers have merged:

openshift/operator-framework-olm#998

Jira Issue OCPBUGS-51246 has been moved to the MODIFIED state.

Details

In response to this:

Upstream-repository: operator-lifecycle-manager
Upstream-commit: dfd0b2bea85038d3c0d65348bc812d297f16b8d2

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-bot · 2025-05-07T21:47:51Z

[ART PR BUILD NOTIFIER]

Distgit: operator-registry
This PR has been included in build operator-registry-container-v4.17.0-202505072107.p0.gb135c38.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-05-07T21:47:55Z

[ART PR BUILD NOTIFIER]

Distgit: operator-lifecycle-manager
This PR has been included in build operator-lifecycle-manager-container-v4.17.0-202505072107.p0.gb135c38.assembly.stream.el9.
All builds following this will include this PR.

openshift-bot · 2025-05-07T21:50:49Z

[ART PR BUILD NOTIFIER]

Distgit: ose-operator-framework-tools
This PR has been included in build ose-operator-framework-tools-container-v4.17.0-202505072107.p0.gb135c38.assembly.stream.el9.
All builds following this will include this PR.

openshift-merge-robot · 2025-05-08T07:59:56Z

Fix included in accepted release 4.17.0-0.nightly-2025-05-08-025554

(vendor) pin go-jose/v4@v4.0.5

f71c731

Upstream-repository: operator-lifecycle-manager Upstream-commit: dfd0b2bea85038d3c0d65348bc812d297f16b8d2

openshift-ci Bot requested review from dinhxuanvu and tmshort May 6, 2025 19:07

openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 6, 2025

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 6, 2025

openshift-ci Bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label May 6, 2025

camilamacedo86 approved these changes May 7, 2025

View reviewed changes

openshift-ci Bot assigned camilamacedo86 May 7, 2025

openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 7, 2025

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 7, 2025

openshift-ci Bot assigned bandrade, emmajiafan, jianzhangbjz, KeenonLee and kuiwang02 May 7, 2025

openshift-ci Bot assigned Xia-Zhao-rh May 7, 2025

openshift-merge-bot Bot merged commit b135c38 into openshift:release-4.17 May 7, 2025
13 checks passed

Conversation

anik120 commented May 6, 2025

Uh oh!

openshift-ci-robot commented May 6, 2025

Uh oh!

anik120 commented May 6, 2025

Uh oh!

openshift-ci-robot commented May 6, 2025

Uh oh!

anik120 commented May 6, 2025

Uh oh!

openshift-ci-robot commented May 6, 2025

Uh oh!

anik120 commented May 6, 2025

Uh oh!

openshift-ci-robot commented May 6, 2025

Uh oh!

bandrade commented May 6, 2025

Uh oh!

perdasilva commented May 7, 2025

Uh oh!

camilamacedo86 left a comment

Choose a reason for hiding this comment

Uh oh!

openshift-ci Bot commented May 7, 2025

Uh oh!

oceanc80 commented May 7, 2025

Uh oh!

openshift-ci-robot commented May 7, 2025

Uh oh!

openshift-ci Bot commented May 7, 2025

Uh oh!

Uh oh!

openshift-ci-robot commented May 7, 2025

Uh oh!

openshift-bot commented May 7, 2025

Uh oh!

openshift-bot commented May 7, 2025

Uh oh!

openshift-bot commented May 7, 2025

Uh oh!

openshift-merge-robot commented May 8, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

13 participants