From d76d3eaa496c8287dd03771355ff2e71e3eceee1 Mon Sep 17 00:00:00 2001 From: Aaron Crickenberger Date: Wed, 15 Sep 2021 15:32:26 -0700 Subject: [PATCH] docs: follow kubernetes/k8s.io branch rename: --- RELEASE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/RELEASE.md b/RELEASE.md index 73837738..7a689687 100644 --- a/RELEASE.md +++ b/RELEASE.md @@ -7,7 +7,7 @@ prometheus-adapter is released on an as-needed basis. The process is as follows: 1. A PR that bumps version hardcoded in code is created and merged 1. An OWNER creates a draft Github release 1. An OWNER creates a release tag using `git tag -s $VERSION`, inserts the changelog and pushes the tag with `git push $VERSION`. Then waits for [prow.k8s.io](https://prow.k8s.io) to build and push new images to [gcr.io/k8s-staging-prometheus-adapter](https://gcr.io/k8s-staging-prometheus-adapter) -1. A PR in [kubernetes/k8s.io](https://github.com/kubernetes/k8s.io/blob/master/k8s.gcr.io/images/k8s-staging-prometheus-adapter/images.yaml) is created to release images to `k8s.gcr.io` +1. A PR in [kubernetes/k8s.io](https://github.com/kubernetes/k8s.io/blob/main/k8s.gcr.io/images/k8s-staging-prometheus-adapter/images.yaml) is created to release images to `k8s.gcr.io` 1. An OWNER publishes the GitHub release 1. An announcement email is sent to `kubernetes-sig-instrumentation@googlegroups.com` with the subject `[ANNOUNCE] prometheus-adapter $VERSION is released` 1. The release issue is closed