From 01577f69a571bcbf207179b78d837a59a8d86d32 Mon Sep 17 00:00:00 2001
From: Ivan FB <128452529+Ivansete-status@users.noreply.github.com>
Date: Wed, 29 May 2024 10:09:35 +0200
Subject: [PATCH] release-process.md: add step to merge the release branch back
 to master (#2734)

---
 docs/contributors/release-process.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/docs/contributors/release-process.md b/docs/contributors/release-process.md
index 9fbf39402..c0fb12d1c 100644
--- a/docs/contributors/release-process.md
+++ b/docs/contributors/release-process.md
@@ -95,6 +95,7 @@ We also need to merge release branch back to master as a final step.
    - Deploy release to the `waku.sandbox` fleet from [Jenkins](https://ci.infra.status.im/job/nim-waku/job/deploy-waku-sandbox/).
    - Ensure that nodes successfully start up and monitor health using [Grafana](https://grafana.infra.status.im/d/qrp_ZCTGz/nim-waku-v2?orgId=1) and [Kibana](https://kibana.infra.status.im/goto/a7728e70-eb26-11ec-81d1-210eb3022c76).
    - If necessary, revert by deploying the previous release. Download logs and open a bug report issue.
+5. Submit a PR to merge the release branch back to `master`. Make sure you use the option `Merge pull request (Create a merge commit)` to perform such merge.
 
 ### Performing a patch release