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

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

Merged
merged 1 commit into from
Sep 9, 2021

Conversation

alanfx
Copy link
Collaborator

@alanfx alanfx commented Sep 9, 2021

No description provided.

@openshift-ci
Copy link

openshift-ci bot commented Sep 9, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alanfx

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:

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

@alanfx
Copy link
Collaborator Author

alanfx commented Sep 9, 2021

OCF Webhook is merging this PR

@alanfx alanfx merged commit 9cc25ea into release-next Sep 9, 2021
ReToCode pushed a commit to ReToCode/eventing-kafka that referenced this pull request Jan 3, 2023
bumping knative.dev/pkg 6040b3a...0d31134:
  > 0d31134 Fix nil pointer panic in kvstore (# 2002)
bumping knative.dev/eventing 81ce898...ea452b5:
  > ea452b5 go 1.15 in go.mod, drop k8s 1.17 e2e tests (# 4795)
  > ce099cf new cloudevent extension attribute with dispatch error (# 4760)
  > 83ecc7c Set failure policy to ignore for webhook (# 4793)
  > ae17ca3 Adding HPA for eventing-webhook (# 4792)

Signed-off-by: Knative Automation <automation@knative.team>
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