OCPBUGS-29613: UPSTREAM: <carry>: bump structured-merge-diff

[stevekuznetsov]

No description provided.

[openshift-ci-robot]

@stevekuznetsov: This pull request references Jira Issue OCPBUGS-29613, which is valid.

4 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-29758 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request.

The bug has been updated to refer to the pull request using the external bug tracker.

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-robot]

@stevekuznetsov: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• c39ca5b|UPSTREAM: : bump structured-merge-diff: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[openshift-ci-robot]

@stevekuznetsov: This pull request references Jira Issue OCPBUGS-29613, which is valid.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.15.0) matches configured target version for branch (4.15.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-29758 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
• dependent Jira Issue OCPBUGS-29758 targets the "4.16.0" version, which is one of the valid target versions: 4.16.0
• bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Jira (jiezhao@redhat.com), skipping review request.

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-robot]

@stevekuznetsov: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• a475cc4|UPSTREAM: : bump structured-merge-diff: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[soltysh]

/lgtm
/approve

/remove-label backports/unvalidated-commits
/label backports/validated-commits

[soltysh]

/hold
this will merge after we land the bump from #1891

[openshift-ci-robot]

@stevekuznetsov: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• a475cc4|UPSTREAM: : bump structured-merge-diff: does not specify an upstream backport in the commit message
• e5adc1d|fix intergration test: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[stevekuznetsov]

Updated integration test from the other commit in upstream PR 119334

[openshift-ci-robot]

@stevekuznetsov: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

• a475cc4|UPSTREAM: : bump structured-merge-diff: does not specify an upstream backport in the commit message
• cf7d9fa|UPSTREAM: : fix intergration test: does not specify an upstream backport in the commit message

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

[soltysh]

/lgtm

/remove-label backports/unvalidated-commits
/label backports/validated-commits

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: soltysh, stevekuznetsov

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:

• DOWNSTREAM_OWNERS [soltysh]

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

[stevekuznetsov]

@soltysh this is ready, are we good to go?

[stevekuznetsov]

/hold cancel

[openshift-ci]

@stevekuznetsov: 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/test-infra repository. I understand the commands that are listed here.

[openshift-ci-robot]

@stevekuznetsov: Jira Issue OCPBUGS-29613: All pull requests linked via external trackers have merged:

• openshift/hypershift#3612
• openshift/kubernetes#1893

Jira Issue OCPBUGS-29613 has been moved to the MODIFIED state.

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-bot]

[ART PR BUILD NOTIFIER]

This PR has been included in build openshift-enterprise-pod-container-v4.15.0-202405021635.p0.g8ca71f7.assembly.stream.el9 for distgit openshift-enterprise-pod.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.15.0-0.nightly-2024-05-04-030917