From c9422e016d749132f5c72b0fc9fe845abb96cac2 Mon Sep 17 00:00:00 2001
From: Anthony Martin <38542602+anthony-c-martin@users.noreply.github.com>
Date: Tue, 1 Aug 2023 13:20:03 -0400
Subject: [PATCH] Update release-checklist.md (#11433)

###### Microsoft Reviewers:
codeflow:open?pullrequest=https://github.com/Azure/bicep/pull/11433&drop=dogfoodAlpha
---
 docs/release-checklist.md | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/docs/release-checklist.md b/docs/release-checklist.md
index 93d5bc0eb23..d4813fa887b 100644
--- a/docs/release-checklist.md
+++ b/docs/release-checklist.md
@@ -16,11 +16,10 @@
 1. Review history for changes to [bicepconfig.schema.json](https://github.com/Azure/bicep/commits/main/src/vscode-bicep/schemas/bicepconfig.schema.json). Raise an issue for any recently-added linter rules which do not have public documentation.
 1. (**end-of-month releases only**) Bump the version number by incrementing the minor version number in [this file](https://github.com/Azure/bicep/blob/main/version.json) (example [here](https://github.com/Azure/bicep/pull/9698))
 1. Run the Official Build (see [this README](https://msazure.visualstudio.com/One/_git/BicepMirror) for instructions).
-1. Get version number from official build by looking at the artifacts and push a new tag to the Bicep repo. This should be of format `vXX.YY.ZZ` - e.g `v0.14.85`.
-    1. In the Bicep repo, make sure you are on the main branch and on the commit that matches the submodule commit that triggers the official build in the BicepMirror repository.
-        - This can be done by running `git reset <submodule_commit_id> --hard` in your local Bicep repository folder.
-    1. Run git tag v<new_release_number> (ex: git tag v0.15.31)
-    1. Run git push origin v<new_release_number> (ex: git push origin v0.15.31)
+1. Push the version tag for the commit used to generate the official build.
+    1. Obtain the version number from official build by looking at the official build artifacts. This should be of format `vXX.YY.ZZ` - e.g `v0.14.85`.
+    1. In the Bicep repo, run `git tag v<new_release_number> <commit_hash>`, where `<commit_hash>` is the git commit hash used for the official build (ex: `git tag v0.15.31 3ba6e06a8d412febd182e607d0f5fe607ec90274`).
+    1. Run `git push origin v<new_release_number>` to push the tag (ex: `git push origin v0.15.31`).
 1. [Create a draft release](https://github.com/Azure/bicep/releases/new) for the new tag and set release title to the tag name. Use the "Save draft" button to save the changes without publishing it.
 1. Run `bicep/scripts/CreateReleaseNotes -FromTag <previous tag> -ToTag <new tag>` and set the output as the release description.
     1. Give the output of this script to a PM, and ask them to clean up the notes for the release.