From a0fd407d2315a7d45b88e05b48203e0deb4a8a1a Mon Sep 17 00:00:00 2001
From: James Rich <2199651+jamesarich@users.noreply.github.com>
Date: Tue, 9 Sep 2025 17:06:53 -0500
Subject: [PATCH] docs(RELEASE_PROCESS): update release finalization steps
 (#3040)

---
 RELEASE_PROCESS.md | 18 ++++++++----------
 1 file changed, 8 insertions(+), 10 deletions(-)

diff --git a/RELEASE_PROCESS.md b/RELEASE_PROCESS.md
index 8eff7360b..04ba017b5 100644
--- a/RELEASE_PROCESS.md
+++ b/RELEASE_PROCESS.md
@@ -77,16 +77,14 @@ git push origin v2.3.5-closed.1
 ```
 This triggers the workflow again, but this time it will send the build to the `NewAlpha` track for your closed testers. You can then continue the cycle of testing, fixing, and promoting all the way to production.
 
-### 4. Merging Back to `main`
-After the final production release is complete and verified, merge the release branch back into `main` to ensure any hotfixes are included. Then, delete the release branch.
-```bash
-git checkout main
-git pull origin main
-git merge release/2.3.5
-git push origin main
-git branch -d release/2.3.5
-git push origin --delete release/2.3.5
-```
+### 4. Finalizing the Release
+After the final production release is complete and verified, open a Pull Request to merge the release branch back into `main`. This ensures any hotfixes applied during the release cycle are properly reviewed and integrated.
+
+*   **Title:** `Release/2.3.5`
+*   **Base Branch:** `main`
+*   **Compare Branch:** `release/2.3.5`
+
+Once the PR is approved and merged, you can safely delete the release branch.
 
 ## Manual Finalization Steps