From d723e870a21e658827c5867bbaec6ccbf1d55477 Mon Sep 17 00:00:00 2001
From: Rafael Gonzaga <rafael.nunu@hotmail.com>
Date: Thu, 6 Jul 2023 09:54:51 -0300
Subject: [PATCH] doc: mention git node release prepare
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
PR-URL: https://github.com/nodejs/node/pull/48644
Reviewed-By: Ruy Adorno <ruyadorno@google.com>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
---
 doc/contributing/releases.md | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md
index b91ef8443269e4..368a2bda3d594c 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.