google / knative-gcp

GCP event implementations to use with Knative Eventing.
https://github.com/knative/eventing
Apache License 2.0
159 stars 75 forks source link

[main] Upgrade to latest dependencies #2168

Closed knative-automation closed 3 years ago

knative-automation commented 3 years ago

Cron. -knative-prow-robot

/cc @nlopezgi @zhongduo /assign @nlopezgi @zhongduo

Produced via:

./hack/update-deps.sh --upgrade --release v0.22
./hack/update-codegen.sh

Details:

bumping knative.dev/serving e9ea07e...c508400:
  > c508400 Update net-kourier nightly (# 10887)
  > 3ee7319 upgrade to latest dependencies (# 10884)
  > 267697a Add DomainMapping namespace label annotation (# 10868)
  > c4e05e5 Lint use of type-safe atomics (# 10882)
  > 9419b6a Update net-kourier nightly (# 10877)
  > 6d84c5b Don't override the queue-proxy image on pre-upgrade tests (# 10872)
  > 0b07d94 Parallelise tests in activator/net (# 10880)
  > 4301fa1 Update net-contour nightly (# 10876)
  > eb873de Update net-istio nightly (# 10875)
  > 79faf2b Use type-safe atomics (# 10881)
  > 94451d1 Make sure to reinitialise loop var in parallel tests (# 10879)
  > 041dca1 upgrade to latest dependencies (# 10874)
bumping knative.dev/eventing 21bcd68...ef6d89e:
  > ef6d89e upgrade to CRDv1, add more unit tests around the workings of event types (# 5013)
  > d6d48a7 add unit tests to reconciler/source/config_watcher (# 5012)
bumping knative.dev/pkg 08fc626...8fbab7e:
  > 8fbab7e Redo the comment a bit further (# 2042)
knative-prow-robot commented 3 years ago

Hi @knative-automation. Thanks for your PR.

I'm waiting for a google member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
nlopezgi commented 3 years ago

/ok-to-test /lgtm /approve

knative-prow-robot commented 3 years ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: nlopezgi

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: - ~~[OWNERS](https://github.com/google/knative-gcp/blob/main/OWNERS)~~ [nlopezgi] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
nlopezgi commented 3 years ago

/hold

nlopezgi commented 3 years ago

holding off till https://github.com/google/knative-gcp/pull/2169 is in and 0.21 branch is cut

knative-prow-robot commented 3 years ago

@knative-automation: The following test failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
pull-google-knative-gcp-wi-tests cb8c0bd1dcbbbe2e77f4f44b5e3052bcacf68e83 link /test pull-google-knative-gcp-wi-tests

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
knative-prow-robot commented 3 years ago

New changes are detected. LGTM label has been removed.

nlopezgi commented 3 years ago

closing as the merge did not work properly, lets just wait for the bot to create a new PR.