From 6d69297ee2080b7e61d9ac6c7067e08ece22411f Mon Sep 17 00:00:00 2001 From: Jeff Handley Date: Sat, 10 May 2025 08:49:55 -0700 Subject: [PATCH] Make small corrections to release process docs The 'auto' selection for the previous tag has been working well. And this also fixes a typo. --- .github/workflows/release.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/.github/workflows/release.md b/.github/workflows/release.md index 834f56b44..280c35383 100644 --- a/.github/workflows/release.md +++ b/.github/workflows/release.md @@ -15,8 +15,7 @@ The following process is used when publishing new releases to NuGet.org: - Click the 'Target' dropdown button - Choose the 'Recent Commits' tab - Select the commit to use for the release, ensuring it's one from above where CI is known to be green - - Click the 'Previous tag' dropdown button - - Choose the previous release to use for generating release notes + - The 'Previous tag' dropdown can remain on 'Auto' unless the previous release deviated from this process - Click the 'Generate release notes button' - This will add release notes into the Release description - The generated release notes include what has changed and the list of new contributors @@ -26,7 +25,7 @@ The following process is used when publishing new releases to NuGet.org: - Augment the Release description as desired - This content is presented used on GitHub and is not persisted into any artifacts - Check the 'Set as a pre-release' button under the release description if appropriate - - Click 'Public release' + - Click 'Publish release' 3. **Monitor the Release workflow** - After publishing the release, a workflow will begin for producing the release's build artifacts and publishing the NuGet package to NuGet.org