Skip to content

Commit fce7a86

Browse files
authored
Merge pull request #11652 from fabriziopandini/fix-broken-links
🐛 Fix broken links in release team handbooks
2 parents 2c7219e + c7445f3 commit fce7a86

File tree

1 file changed

+1
-1
lines changed
  • docs/release/role-handbooks/release-lead

1 file changed

+1
-1
lines changed

docs/release/role-handbooks/release-lead/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,7 @@ to a newer Go minor version according to our [backport policy](./../../../../CON
173173

174174
1. Ensure CI is stable before cutting the release (e.g. by checking with the CI manager)
175175
Note: special attention should be given to image scan results, so we can avoid cutting a release with CVE or document known CVEs in release notes.
176-
2. Ask the [Communications/Docs/Release Notes Manager](#communicationsdocsrelease-notes-manager) to [create a PR with the release notes](#create-pr-for-release-notes) for the new desired tag and review the PR. Once the PR merges, it will trigger a [GitHub Action](https://github.com/kubernetes-sigs/cluster-api/actions/workflows/release.yaml) to create a release branch, push release tags, and create a draft release. This will also trigger a [ProwJob](https://prow.k8s.io/?repo=kubernetes-sigs%2Fcluster-api&job=post-cluster-api-push-images) to publish images to the staging repository.
176+
2. Ask the [Communications/Docs/Release Notes Manager](../communications/README.md) to [create a PR with the release notes](../communications/README.md#create-pr-for-release-notes) for the new desired tag and review the PR. Once the PR merges, it will trigger a [GitHub Action](https://github.com/kubernetes-sigs/cluster-api/actions/workflows/release.yaml) to create a release branch, push release tags, and create a draft release. This will also trigger a [ProwJob](https://prow.k8s.io/?repo=kubernetes-sigs%2Fcluster-api&job=post-cluster-api-push-images) to publish images to the staging repository.
177177
3. Promote images from the staging repository to the production registry (`registry.k8s.io/cluster-api`):
178178
1. Wait until images for the tag have been built and pushed to the [staging repository](https://console.cloud.google.com/gcr/images/k8s-staging-cluster-api) by the [post push images job](https://prow.k8s.io/?repo=kubernetes-sigs%2Fcluster-api&job=post-cluster-api-push-images).
179179
2. If you don't have a GitHub token, create one by going to your GitHub settings, in [Personal access tokens](https://github.com/settings/tokens). Make sure you give the token the `repo` scope.

0 commit comments

Comments
 (0)