🤖 Triggering CI on branch 'release-next' after synching to upstream/main

[serverless-qe]

No description provided.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 31f744b and 2 for PR HEAD 1c7498d in total

[openshift-ci]

New changes are detected. LGTM label has been removed.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by: serverless-qe

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:

• OWNERS

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

[openshift-ci]

@serverless-qe: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/4.13-e2e-aws-ocp	2b1ab70	link	true	/test 4.13-e2e-aws-ocp
ci/prow/4.13-images	2b1ab70	link	true	/test 4.13-images

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.