From 0fd3e27dcdf9cddcb7113d0fc46f85c1e7b98204 Mon Sep 17 00:00:00 2001 From: Jover Date: Thu, 15 Dec 2022 13:44:50 -0800 Subject: [PATCH] Update release docs Add in steps for release that are not completely automated yet based on my experience with the last two releases of Augur. --- docs/contribute/DEV_DOCS.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/contribute/DEV_DOCS.md b/docs/contribute/DEV_DOCS.md index 8ad3bae59..d864e2edd 100644 --- a/docs/contribute/DEV_DOCS.md +++ b/docs/contribute/DEV_DOCS.md @@ -187,6 +187,13 @@ Versions for this project, Augur, from 3.0.0 onwards aim to follow the 2. In **New version X.X.X**, provide the new version number. 3. Select **Run workflow**. 3. Ensure workflow runs successfully. + - Ensure the [docker-base CI action triggered by nextstrain-bot](https://github.com/nextstrain/docker-base/actions/workflows/ci.yml?query=branch%3Amaster+actor%3Anextstrain-bot) runs successfully. +4. Create a [new GitHub release](https://github.com/nextstrain/augur/releases/new). + 1. Choose the tag for the new version number. + 2. In **Release title**, provide the new version number. + 3. In **Describe this release**, copy over changes for this new version from [CHANGES.md](../../CHANGES.md). + 4. Ensure **Set as the latest release** is checked. + 5. Publish release. ##### 4. Update on Bioconda @@ -209,6 +216,13 @@ For versions with dependency changes: [bioconda-recipes]: https://github.com/bioconda/bioconda-recipes/pull/34509 +##### 5. Build/Release Nextstrain/conda-base + +1. Wait for the bioconda-recipe PR to be merged. +2. Wait for the new version of Augur to be available in on bioconda. +3. Manually run the [conda-base CI workflow](https://github.com/nextstrain/conda-base/actions/workflows/ci.yaml) on the `master` branch. +4. Ensure workflow runs successfully. + #### Notes New releases are tagged in git using an "annotated" tag. If the git option