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

Release v1.9.4 #10568

Merged
merged 1 commit into from
Oct 25, 2023
Merged

Release v1.9.4 #10568

merged 1 commit into from
Oct 25, 2023

Conversation

rikatz
Copy link
Contributor

@rikatz rikatz commented Oct 25, 2023

Release v1.9.4

@netlify
Copy link

netlify bot commented Oct 25, 2023

Deploy Preview for kubernetes-ingress-nginx canceled.

Name Link
🔨 Latest commit c0962b4
🔍 Latest deploy log https://app.netlify.com/sites/kubernetes-ingress-nginx/deploys/653930f43bc3ec0008104e11

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 25, 2023
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. approved Indicates a PR has been approved by an approver from all required OWNERS files. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Oct 25, 2023
@k8s-ci-robot k8s-ci-robot added needs-priority area/helm Issues or PRs related to helm charts size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 25, 2023
@rikatz rikatz force-pushed the release-194-final-bla branch 2 times, most recently from da234b5 to 63b8052 Compare October 25, 2023 15:09
@rikatz rikatz force-pushed the release-194-final-bla branch from 63b8052 to c0962b4 Compare October 25, 2023 15:14
@strongjz
Copy link
Member

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Oct 25, 2023
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: rikatz, strongjz

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

@k8s-ci-robot k8s-ci-robot merged commit 5583f90 into kubernetes:main Oct 25, 2023
38 checks passed
@strongjz
Copy link
Member

/cherry-pick release-1.9

@k8s-infra-cherrypick-robot
Copy link
Contributor

@strongjz: #10568 failed to apply on top of branch "release-1.9":

Applying: Release v1.9.4
.git/rebase-apply/patch:46: trailing whitespace.
 
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M	README.md
M	charts/ingress-nginx/Chart.yaml
M	charts/ingress-nginx/README.md
M	charts/ingress-nginx/values.yaml
M	deploy/static/provider/aws/deploy.yaml
M	deploy/static/provider/aws/nlb-with-tls-termination/deploy.yaml
M	deploy/static/provider/baremetal/deploy.yaml
M	deploy/static/provider/cloud/deploy.yaml
M	deploy/static/provider/do/deploy.yaml
M	deploy/static/provider/exoscale/deploy.yaml
M	deploy/static/provider/kind/deploy.yaml
M	deploy/static/provider/oracle/deploy.yaml
M	deploy/static/provider/scw/deploy.yaml
Falling back to patching base and 3-way merge...
Auto-merging deploy/static/provider/scw/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/scw/deploy.yaml
Auto-merging deploy/static/provider/oracle/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/oracle/deploy.yaml
Auto-merging deploy/static/provider/kind/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/kind/deploy.yaml
Auto-merging deploy/static/provider/exoscale/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/exoscale/deploy.yaml
Auto-merging deploy/static/provider/do/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/do/deploy.yaml
Auto-merging deploy/static/provider/cloud/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/cloud/deploy.yaml
Auto-merging deploy/static/provider/baremetal/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/baremetal/deploy.yaml
Auto-merging deploy/static/provider/aws/nlb-with-tls-termination/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/aws/nlb-with-tls-termination/deploy.yaml
Auto-merging deploy/static/provider/aws/deploy.yaml
CONFLICT (content): Merge conflict in deploy/static/provider/aws/deploy.yaml
Auto-merging charts/ingress-nginx/values.yaml
CONFLICT (content): Merge conflict in charts/ingress-nginx/values.yaml
Auto-merging charts/ingress-nginx/README.md
CONFLICT (content): Merge conflict in charts/ingress-nginx/README.md
Auto-merging charts/ingress-nginx/Chart.yaml
CONFLICT (content): Merge conflict in charts/ingress-nginx/Chart.yaml
Auto-merging README.md
CONFLICT (content): Merge conflict in README.md
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Release v1.9.4
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-1.9

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/helm Issues or PRs related to helm charts cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants