From ba6745c7b6f84ad74d9a742358788f1922b25224 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C3=ABl=20Valais?= Date: Fri, 29 Mar 2024 14:11:32 +0100 Subject: [PATCH] release: cmctl no longer shipped as part of cert-manager releases MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Cmctl now lives in its own repository. Signed-off-by: Maël Valais --- content/docs/contributing/release-process.md | 15 ++------------- 1 file changed, 2 insertions(+), 13 deletions(-) diff --git a/content/docs/contributing/release-process.md b/content/docs/contributing/release-process.md index 5167ec3b42f..b4fbe8087b9 100644 --- a/content/docs/contributing/release-process.md +++ b/content/docs/contributing/release-process.md @@ -385,7 +385,7 @@ page if a step is missing or if it is outdated. > kicking off a build using the steps in `gcb/build_cert_manager.yaml`. Users with access to > the cert-manager-release project on GCP should be able to view logs in [GCB build history](https://console.cloud.google.com/cloud-build/builds?project=cert-manager-release). -9. **(1.12 and above)** In this step, we make sure the Go module +9. **(1.12, 1.13, and 1.14)** In this step, we make sure the Go module `github.com/cert-manager/cert-manager/cmd/ctl` can be imported by third-parties. @@ -452,7 +452,6 @@ page if a step is missing or if it is outdated. [how-are-versions-of-a-sub-module-managed]: https://stackoverflow.com/questions/60601011/how-are-versions-of-a-sub-module-managed/60601402#60601402 - 10. In this section, we will be creating the description for the GitHub Release. > **Note:** This step is about creating the description that will be @@ -472,7 +471,7 @@ page if a step is missing or if it is outdated. ```bash # Must be run from the cert-manager folder. - export GITHUB_TOKEN=*your-token* + export GITHUB_TOKEN=$(gh auth token) git fetch origin $BRANCH export START_SHA="$(git rev-list --reverse --ancestry-path $(git merge-base $START_TAG $BRANCH)..$BRANCH | head -1)" release-notes --debug --repo-path cert-manager \ @@ -509,16 +508,6 @@ page if a step is missing or if it is outdated. properly redacted but sometimes we forget to update this.

- > **NOTE (1.10 and earlier):** If you're releasing an older version of - > cert-manager then the automatic build will failed because the GCB - > config for that build wasn't backported. In this case, you'll need to - > trigger the build manually using `cmrel`, which takes about 5 minutes: - > - > ```bash - > # Must be run from the "cert-manager/release" repo folder. - > cmrel makestage --ref=$RELEASE_VERSION - > ``` - 3. Copy the build logs URL and send a second Slack message in reply to this first message with the Cloud Build job link. For example, the message might look like: