From 5c95d7a838452e9169a856ffbbdc48aec160abff Mon Sep 17 00:00:00 2001 From: Steve Kriss Date: Mon, 12 Feb 2024 14:36:27 -0700 Subject: [PATCH] drop Kubernetes version vars from patch release process They don't need to be set since the changelog is now generated manually for patch releases, one less thing to have to look up/fill in. Signed-off-by: Steve Kriss --- site/content/resources/release-process.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/site/content/resources/release-process.md b/site/content/resources/release-process.md index ed67adf1f25..4a3057c4d52 100644 --- a/site/content/resources/release-process.md +++ b/site/content/resources/release-process.md @@ -47,7 +47,7 @@ export CONTOUR_UPSTREAM_REMOTE_NAME=upstream 1. Check out `main`, ensure it's up to date, and ensure you have a clean working directory. 1. Create a new local feature branch from `main`. 1. Generate a new set of versioned docs, plus a changelog: - + ```bash go run ./hack/release/prepare-release.go $CONTOUR_RELEASE_VERSION $KUBERNETES_MIN_VERSION $KUBERNETES_MAX_VERSION ``` @@ -144,9 +144,6 @@ export CONTOUR_RELEASE_VERSION_MAJOR=1 export CONTOUR_RELEASE_VERSION_MINOR=11 export CONTOUR_PREVIOUS_VERSION=v1.11.0 -export KUBERNETES_MIN_VERSION=1.20 -export KUBERNETES_MAX_VERSION=1.22 - export CONTOUR_UPSTREAM_REMOTE_NAME=upstream ```