diff --git a/content/docs/contributing/release-process.md b/content/docs/contributing/release-process.md
index 54d4d47584..c31d279040 100644
--- a/content/docs/contributing/release-process.md
+++ b/content/docs/contributing/release-process.md
@@ -498,6 +498,7 @@ page if a step is missing or if it is outdated.
release-notes --debug --repo-path cert-manager \
--org cert-manager --repo cert-manager \
--required-author "jetstack-bot" \
+ --markdown-links=false \
--output github-release-description.md
```
@@ -523,33 +524,34 @@ page if a step is missing or if it is outdated.
Releasing 1.2.0-alpha.2
๐งต
- ๐ฐ Please have a quick look at the build log as it might contain some unredacted - data that we forgot to hide. We try to make sure the sensitive data is - properly redacted but sometimes we forget to update this. -
+ ๐ฐ Please have a quick look at the build log as it might contain some unredacted + data that we forgot to hide. We try to make sure the sensitive data is + properly redacted but sometimes we forget to update this. +
cmrel makestage
build logs: https://console.cloud.google.com/cloud-build/builds/7641734d-fc3c-42e7-9e4c-85bfc4d1d547?project=1021342095237
cmrel publish
build: https://console.cloud.google.com/cloud-build/builds/b6fef12b-2e81-4486-9f1f-d00592351789?project=1021342095237
-14. Publish the GitHub release:
+13. Publish the GitHub release:
1. Visit the draft GitHub release and paste in the release notes that you
generated earlier. You will need to manually edit the content to match
@@ -612,7 +614,7 @@ page if a step is missing or if it is outdated.
4. Click "Publish" to make the GitHub release live.
-15. Merge the pull request containing the Helm chart:
+14. Merge the pull request containing the Helm chart:
The Helm charts for cert-manager are served using Cloudflare pages and the
Helm chart files and metadata are stored in the
@@ -627,7 +629,7 @@ page if a step is missing or if it is outdated.
5. Check that the
[cert-manager Helm chart is visible on ArtifactHUB](https://artifacthub.io/packages/helm/cert-manager/cert-manager).
-16. **(final + patch releases)** Merge the 4 Website PRs:
+15. **(final + patch releases)** Merge the 4 Website PRs:
1. Merge the PRs "Release Notes", "Upgrade Notes", and "Freeze And Bump
Versions" that you have created previously.
@@ -646,7 +648,7 @@ page if a step is missing or if it is outdated.
[ff-release-next]:
https://github.com/cert-manager/website/compare/master...release-next?quick_pull=1&title=%5BPost-Release%5D+Merge+release-next+into+master&body=%3C%21--%0A%0AThe+command+%22%2Foverride+dco%22+is+necessary+because+some+the+merge+commits%0Ahave+been+written+by+the+bot+and+do+not+have+a+DCO+signoff.%0A%0A--%3E%0A%0A%2Foverride+dco
-17. Open a PR for a [Homebrew](https://github.com/Homebrew/homebrew-core/pulls)
+16. Open a PR for a [Homebrew](https://github.com/Homebrew/homebrew-core/pulls)
formula update for `cmctl`.
Assuming you have `brew` installed, you can use the `brew bump-formula-pr`
@@ -664,7 +666,7 @@ page if a step is missing or if it is outdated.
against https://github.com/homebrew/homebrew-core has been opened, continue
with further release steps.
-18. Post a Slack message as an answer to the first message. Toggle the check box
+17. Post a Slack message as an answer to the first message. Toggle the check box
"Also send to `#cert-manager-dev`" so that the message is well visible. Also
cross-post the message on `#cert-manager`.