-
Notifications
You must be signed in to change notification settings - Fork 423
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
updating release-0.6 branch to cut a new release #710
updating release-0.6 branch to cut a new release #710
Conversation
Hi @jaidevmane. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
/retest |
dc9dd6c
to
cd879bc
Compare
cd879bc
to
ec90e2d
Compare
/retest |
Unknown CLA label state. Rechecking for CLA labels. Send feedback to sig-contributor-experience at kubernetes/community. /check-cla |
ec90e2d
to
93ba2bb
Compare
/retest |
…app-k8s-dependencies chore: Update app K8s dependencies
…rovers adding new approvers - nnmin-aws
updating k8s client libraries and go version
…ci-versions chore: Update CI action versions, remove `push` trigger
4cfb6c3
to
8f581ef
Compare
/lgtm |
@haoranleo: changing LGTM is restricted to collaborators 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 kubernetes/test-infra repository. |
/lgtm |
…rpc-to-v0.51.0 updating google.golang.org/grpc/otelgrpc to v0.47.0
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jaidevmane, nnmin-aws, wongma7 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 |
/hold |
What this PR does / why we need it:
Updating the release 0.6 branch to pull in changes from master.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #