Skip to content

OPRUN-4194: Update OCP catalogs to v4.21 #518

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 1 commit into from
Oct 15, 2025
Merged

OPRUN-4194: Update OCP catalogs to v4.21 #518

merged 1 commit into from
Oct 15, 2025

Conversation

tmshort
Copy link
Contributor

@tmshort tmshort commented Oct 13, 2025

Use the new method to update catalog versions.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Oct 13, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 13, 2025 •
edited by openshift-ci bot
Loading

@tmshort: This pull request references OPRUN-4197 which is a valid jira issue.

In response to this:

Use the new method to update catalog versions.

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 do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 13, 2025
@openshift-ci openshift-ci bot requested review from pedjak and perdasilva October 13, 2025 14:46
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Oct 13, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tmshort

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

The pull request process is described here

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 Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 13, 2025
This was referenced Oct 13, 2025
Merged
Closed
@tmshort
Copy link
Contributor Author

tmshort commented Oct 13, 2025

/unhold
#519 merged

@tmshort tmshort force-pushed the update-catalog-versions branch from 9596818 to d8b2ca3 Compare October 13, 2025 18:58
@tmshort tmshort changed the title WIP: OPRUN-4197: Update OCP catalogs to v4.21 OPRUN-4197: Update OCP catalogs to v4.21 Oct 13, 2025
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 13, 2025
@camilamacedo86
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 13, 2025
@camilamacedo86
Copy link
Contributor

But we should wait this #521 get merged and close and re-open this one to ensure that default test catalog will be executed with after openshift/release#70215 to ensure that all pass before get merged

Besides I executed those tests locally and all worked
That is just for safety

/hold until #521 get merged

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 13, 2025
@tmshort tmshort changed the title OPRUN-4197: Update OCP catalogs to v4.21 OPRUN-4194: Update OCP catalogs to v4.21 Oct 13, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 13, 2025 •
edited by openshift-ci bot
Loading

@tmshort: This pull request references OPRUN-4194 which is a valid jira issue.

In response to this:

Use the new method to update catalog versions.

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
Copy link
Contributor Author

tmshort commented Oct 14, 2025

/unhold
#521 was merged

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 14, 2025
@jianzhangbjz
Copy link
Contributor

/verified by pass

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Oct 15, 2025
@openshift-ci-robot
Copy link

@jianzhangbjz: This PR has been marked as verified by pass.

In response to this:

/verified by pass

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
Copy link

/retest-required

Remaining retests: 0 against base HEAD 90debf7 and 2 for PR HEAD d8b2ca3 in total

@camilamacedo86
Copy link
Contributor

/retest-required

@openshift-merge-bot openshift-merge-bot bot merged commit 15b4d00 into openshift:main Oct 15, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@pedjak pedjak Awaiting requested review from pedjak

@perdasilva perdasilva Awaiting requested review from perdasilva

Assignees

@camilamacedo86 camilamacedo86

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@tmshort @openshift-ci-robot @camilamacedo86 @jianzhangbjz