OPRUN-4250: Upgrade dependencies (ocp/api, indirect, operator-registry, kube-openapi)

[camilamacedo86]

• upgraded github.com/openshift/api v0.0.0-20251023193535-8691c3014652 => v0.0.0-20251111013132-5c461e21bdb7
• Upgrade indirect dependencies
• upgraded github.com/operator-framework/operator-registry v1.60.0 => v1.61.0
• upgraded k8s.io/kube-openapi v0.0.0-20250710124328-f3f2b991d03b => v0.0.0-20250910181357-589584f1c912

[openshift-ci-robot]

@camilamacedo86: This pull request explicitly references no jira issue.

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• DOWNSTREAM_OWNERS

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

[openshift-ci-robot]

@camilamacedo86: This pull request references OPRUN-4250 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.21.0" version, but no target version was set.

In response to this:

• upgraded github.com/openshift/api v0.0.0-20251023193535-8691c3014652 => v0.0.0-20251111013132-5c461e21bdb7
• Upgrade indirect dependencies
• upgraded github.com/operator-framework/operator-registry v1.60.0 => v1.61.0
• upgraded k8s.io/kube-openapi v0.0.0-20250710124328-f3f2b991d03b => v0.0.0-20250910181357-589584f1c912

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.

[camilamacedo86]

Hey folks,

I am trying to ensure that we have it properly updated with the edge and cleaned
Could you please help me out move forward with this one

@tmshort @anik120 @bandrade

[camilamacedo86]

/test e2e-gcp-console-olm

[openshift-ci]

@camilamacedo86: all tests passed!

Full PR test history. Your PR dashboard.

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.

[tmshort]

Were equivalent changes already done in the dependencies (upstream)? i.e. operator-lifecycle-manager, operator-registry and api?

[camilamacedo86]

Hi @tmshort

From upstream is:
upgraded github.com/operator-framework/operator-registry v1.60.0 => v1.61.0

And we will because release OPM, OLMv0 and OLMv1 today with
See; https://github.com/operator-framework/operator-lifecycle-manager/blob/6838e5e8be6bf78ea11bcc3e7b2964a29df0664e/go.mod#L25

However, good catcher we need bump

• upgraded k8s.io/kube-openapi and ocp/api in upstream

I will do that tomorrow.

/hold

[camilamacedo86]

/hold

[camilamacedo86]

I will create one pr with all.