Skip to content

🤖 triggering CI on branch 'release-next' after synching from upstream/main#370

Open
serverless-qe wants to merge 1 commit intorelease-nextfrom
release-next-ci
Open

🤖 triggering CI on branch 'release-next' after synching from upstream/main#370
serverless-qe wants to merge 1 commit intorelease-nextfrom
release-next-ci

Conversation

@serverless-qe
Copy link
Copy Markdown
Collaborator

No description provided.

@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Mar 20, 2026

New changes are detected. LGTM label has been removed.

@serverless-qe serverless-qe force-pushed the release-next-ci branch 2 times, most recently from 3df0cb5 to 8463ade Compare March 22, 2026 00:51
@serverless-qe serverless-qe force-pushed the release-next branch 2 times, most recently from 28e00c9 to c00e631 Compare March 23, 2026 01:03
@serverless-qe serverless-qe force-pushed the release-next-ci branch 2 times, most recently from 9897020 to dcfd3d4 Compare March 29, 2026 00:50
@serverless-qe serverless-qe force-pushed the release-next branch 2 times, most recently from 6e85750 to 970dc9b Compare March 30, 2026 00:49
@openshift-ci
Copy link
Copy Markdown

openshift-ci Bot commented Apr 12, 2026

[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:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant