From 5a378e7a55a474c5a6a3526c9823c58c0bacd3c1 Mon Sep 17 00:00:00 2001 From: Ivan Valdes Date: Thu, 5 Dec 2024 16:08:16 -0800 Subject: [PATCH] docs: Add note on releasing a pre-release Signed-off-by: Ivan Valdes --- Documentation/contributor-guide/release.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Documentation/contributor-guide/release.md b/Documentation/contributor-guide/release.md index ebf0d4d3f0b..266b500d1c4 100644 --- a/Documentation/contributor-guide/release.md +++ b/Documentation/contributor-guide/release.md @@ -84,6 +84,10 @@ which don't need to be executed before releasing each version. - `git clone --branch release-3.X git@github.com:etcd-io/etcd.git` 6. Run the release script under the repository's root directory, replacing `${VERSION}` with a value without the `v` prefix, i.e. `3.5.13`. - `DRY_RUN=false ./scripts/release.sh ${VERSION}` + - **NOTE:** When doing a pre-release (i.e., a version from the main branch, 3.6.0-alpha.2), you will need to explicitly set the branch to main: + ``` + DRY_RUN=false BRANCH=main ./scripts/release.sh ${VERSION} + ``` It generates all release binaries under the directory `/tmp/etcd-release-${VERSION}/etcd/release/` and images. Binaries are pushed to the Google Cloud bucket under project `etcd-development`, and images are pushed to `quay.io` and `gcr.io`.