Skip to content

[release-4.19] NO-ISSUE: Fix (vendoring and deps/) & refresh rebase for 4.19#5822

Merged
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.19from
pmtk:rebase-r-4.19-fix-rebase-4.19.0-0.nightly-2025-11-25-011336_amd64-2025-11-25_arm64-2025-11-27
Nov 28, 2025
Merged

[release-4.19] NO-ISSUE: Fix (vendoring and deps/) & refresh rebase for 4.19#5822
openshift-merge-bot[bot] merged 3 commits intoopenshift:release-4.19from
pmtk:rebase-r-4.19-fix-rebase-4.19.0-0.nightly-2025-11-25-011336_amd64-2025-11-25_arm64-2025-11-27

Conversation

@pmtk
Copy link
Member

@pmtk pmtk commented Nov 27, 2025

No description provided.

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

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

Details

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 requested review from agullon and dhensel-rh November 27, 2025 16:41
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 27, 2025
@pmtk pmtk changed the title [release-4.19] NO-ISSUE: Fix & refresh rebase for 4.19 [release-4.19] NO-ISSUE: Fix (vendoring and deps/) & refresh rebase for 4.19 Nov 27, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 27, 2025

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

@ggiguash
Copy link
Contributor

/lgtm

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

openshift-ci bot commented Nov 28, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ggiguash, pmtk

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:

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

@pmtk
Copy link
Member Author

pmtk commented Nov 28, 2025

/verified by ci

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

@pmtk: This PR has been marked as verified by ci.

Details

In response to this:

/verified by ci

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.

@pmtk
Copy link
Member Author

pmtk commented Nov 28, 2025

/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Nov 28, 2025
@openshift-merge-bot openshift-merge-bot bot merged commit 918fc65 into openshift:release-4.19 Nov 28, 2025
12 checks passed
@pmtk pmtk deleted the rebase-r-4.19-fix-rebase-4.19.0-0.nightly-2025-11-25-011336_amd64-2025-11-25_arm64-2025-11-27 branch November 28, 2025 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. 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

Development

Successfully merging this pull request may close these issues.

3 participants