From d74071499ff8f0ddac9db69191bd8d513e46a60a Mon Sep 17 00:00:00 2001 From: Jordan Liggitt Date: Mon, 23 Jan 2023 17:29:12 -0500 Subject: [PATCH] Update go compatibility proposal status --- keps/sig-release/3744-stay-on-supported-go-versions/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/keps/sig-release/3744-stay-on-supported-go-versions/README.md b/keps/sig-release/3744-stay-on-supported-go-versions/README.md index 5fa8d290624..f3bcc7116cf 100644 --- a/keps/sig-release/3744-stay-on-supported-go-versions/README.md +++ b/keps/sig-release/3744-stay-on-supported-go-versions/README.md @@ -131,7 +131,7 @@ Feedback to the go team about this situation prompted a [discussion](https://git and a [design](https://go.dev/design/56986-godebug) for improving backward compatibility in go in ways that would allow projects like Kubernetes to use supported go versions while retaining previous go version runtime behavior for a period of time. -With that proposal [likely to be accepted](https://github.com/golang/go/issues/56986#issuecomment-1371307658), +With that proposal [accepted](https://github.com/golang/go/issues/56986#issuecomment-1387606939), and a [request to clarify Kubernetes' approach to updating go versions on release branches](https://github.com/kubernetes/kubernetes/issues/112408), it seemed like a good time to capture requirements and a process for updating Kubernetes release branches.