From 6a24d2b980db831ed7be0bc07247ee359b6ed1aa Mon Sep 17 00:00:00 2001
From: Rafael Gonzaga <rafael.nunu@hotmail.com>
Date: Mon, 3 Jul 2023 11:04:39 -0300
Subject: [PATCH] doc: mention git node release prepare

Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
---
 doc/contributing/releases.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md
index 7e3a2734684a66..00fd536c2a0a50 100644
--- a/doc/contributing/releases.md
+++ b/doc/contributing/releases.md
@@ -264,6 +264,17 @@ You can integrate the PRs into the proposal without running full CI.
 
 ### 2. Create a new branch for the release
 
+⚠️ At this point, you can either run `git node release --prepare`:
+
+```console
+$ git node release --prepare x.y.z
+```
+
+to automate the remaining steps until step 6 or you can perform it manually
+following the below steps.
+
+***
+
 Create a new branch named `vx.y.z-proposal`, off the corresponding staging
 branch.