Skip to content

NO-JIRA: Sync 0.4 with 0.5 #463

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 7 commits into from
Jul 24, 2025
Merged

NO-JIRA: Sync 0.4 with 0.5 #463

merged 7 commits into from
Jul 24, 2025

Conversation

jgbernalp
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot requested review from kyoto and zhuje July 15, 2025 13:28
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 15, 2025
@jgbernalp jgbernalp mentioned this pull request Jul 15, 2025
Open
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 15, 2025

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

@PeterYurkovich
Copy link
Contributor

/lgtm

@PeterYurkovich
Copy link
Contributor

/retitle NO-JIRA: Sync 0.4 with 0.5

@openshift-ci openshift-ci bot changed the title Sync 0.4 with 0.5 NO-JIRA: Sync 0.4 with 0.5 Jul 15, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 15, 2025
@openshift-ci-robot
Copy link

@jgbernalp: 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 openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jul 15, 2025
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jul 15, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jgbernalp, PeterYurkovich

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:
  • OWNERS [PeterYurkovich,jgbernalp]

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

@jgbernalp
Copy link
Contributor Author

/hold until COO 1.2.2 is released

@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 Jul 16, 2025
@jgbernalp
Copy link
Contributor Author

/unhold

@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 Jul 23, 2025
@jgbernalp
Copy link
Contributor Author

/label ux-approved

@openshift-ci openshift-ci bot added the ux-approved Signifies that UX has signed off on this PR label Jul 23, 2025
@etmurasaki
Copy link
Contributor

/label qe-approved
tested on 4.16

@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Jul 24, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 2680d08 into openshift:release-coo-0.4 Jul 24, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@kyoto kyoto Awaiting requested review from kyoto

@zhuje zhuje Awaiting requested review from zhuje

Assignees

@PeterYurkovich PeterYurkovich

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. qe-approved Signifies that QE has signed off on this PR ux-approved Signifies that UX has signed off on this PR
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@jgbernalp @PeterYurkovich @openshift-ci-robot @etmurasaki