Skip to content

Commit

Permalink
drop Kubernetes version vars from patch release process
Browse files Browse the repository at this point in the history
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 <[email protected]>
  • Loading branch information
skriss committed Feb 12, 2024
1 parent 3d78210 commit 5c95d7a
Showing 1 changed file with 1 addition and 4 deletions.
5 changes: 1 addition & 4 deletions site/content/resources/release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
```
Expand Down Expand Up @@ -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
```

Expand Down

0 comments on commit 5c95d7a

Please sign in to comment.