update release process (#7818)

realm · Jun 17, 2024 · 3e0473f · 3e0473f
1 parent 0e2ec0e
commit 3e0473f
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/doc/development/how-to-release.md b/doc/development/how-to-release.md
@@ -4,15 +4,15 @@ The core release process is automated with github [actions](https://github.com/r
   - Select the base branch that you would like to make a release from (usually this will be "master") in the drop down.
   - Enter the version of the new release (eg. "10.123.1" or "4.5.0-CustDemo")
 
-2. This will create a PR, which you should look over and get someone else on the team to review. Verify the changelog by checking the PR description which has a list of commits since the last tag was made. If any changes are required, commit them to this PR's branch.
+2. This will create a PR, which you should look over and get someone else on the team to review. Verify the changelog by checking the PR description which has a list of commits since the last tag was made. If any changes are required, commit them to this PR's branch (please reorder commits such that the version change comes last as the last commit will be the one tagged). Verify that the base commit on the branch you are releasing has passed evergreen checks (or that the failures are known to be spurious and are tracked).
 
-3. When ready, merge the PR. You can squash if there are only "prepare release" changes, but use a "merge-commit" strategy if there are functional changes added manually to the PR (note that if using a merge strategy, the last commit after merge will be the one tagged, so you may want to reorder the commits so that the 'prepare' commit comes last). On merge, the "make-release" action will run. This will:
+3. When ready, merge the PR. You can squash if there are only "prepare release" changes, but use a "merge-commit" strategy if there are functional changes added manually to the PR. On merge, the "make-release" action will run which triggers a Github deployment. Someone from the `@realm/realm-core-team` must approve the deployment for this step to run. Find the Github [deployment](https://github.com/realm/realm-core/actions/workflows/make-release.yml) and approve it. This will:
   - Make a tag
   - Publish the release on Github
   - Open a PR to update the Changelog with the new template section
   - Announce the release in the #appx-releases slack channel
 
-4. Find the newly generated PR that adds the new changelog section. Approve it and merge it.
+4. Find the newly generated PR that adds the new changelog section. Approve it and merge it. It has been discussed by the team that this PR can be approved and merged without initiating evergreen checks because it is an automated change that only affects CHANGELOG.md and originates from an approved template.
 
 ## Previous process