Skip to content
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.

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

[cert-manager-1.15] CM-480: Rebase upstream cert-manager v1.15.5 for cert-manager-operator.v1.15.1 release #246

Open
wants to merge 4 commits into
base: cert-manager-1.15
Choose a base branch
from

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #236

/assign swghosh

@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 13, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: CM-480

In response to this:

This is an automated cherry-pick of #236

/assign swghosh

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 requested review from swghosh and TrilokGeer February 13, 2025 14:55
….com/cert-manager/cert-manager => github.com/openshift/[email protected]
…lifecycle - replaces : cert-manager-operator.v1.15.0 - olm.skipRange: '>=1.15.0 <1.15.1'

+ more manual replaces of upstream version "v1.15.4" => "v1.15.5"
@openshift-cherrypick-robot openshift-cherrypick-robot force-pushed the cherry-pick-236-to-cert-manager-1.15 branch from 24eec4e to 352acac Compare February 13, 2025 14:55
@swghosh
Copy link
Member

swghosh commented Feb 13, 2025

/cc @siddhibhor-56
/lgtm
/label qe-approved
/label px-approved
/label docs-approved
Self adding as this is a cherry-pick, parent PR have had all the required labels.

@openshift-ci openshift-ci bot requested a review from siddhibhor-56 February 13, 2025 14:56
@openshift-ci openshift-ci bot added the qe-approved Signifies that QE has signed off on this PR label Feb 13, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Feb 13, 2025

@openshift-cherrypick-robot: This pull request references CM-480 which is a valid jira issue.

In response to this:

This is an automated cherry-pick of #236

/assign swghosh

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Feb 13, 2025
@openshift-ci openshift-ci bot added px-approved Signifies that Product Support has signed off on this PR docs-approved Signifies that Docs has signed off on this PR labels Feb 13, 2025
@swghosh swghosh removed their assignment Feb 13, 2025
@swghosh
Copy link
Member

swghosh commented Feb 13, 2025

/assign @TrilokGeer
Please approve once tests pass and you're able to review, thank you!

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

openshift-ci bot commented Feb 13, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot, swghosh
Once this PR has been reviewed and has the lgtm label, please assign deads2k 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:

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

@swghosh
Copy link
Member

swghosh commented Feb 13, 2025

/retest-required

Copy link
Contributor

openshift-ci bot commented Feb 13, 2025

@openshift-cherrypick-robot: 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs-approved Signifies that Docs has signed off on this PR 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. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants