From cc62579b2c2cb0870a819a9fa6258b938f4765ee Mon Sep 17 00:00:00 2001
From: Marco Ippolito <marcoippolito54@gmail.com>
Date: Tue, 27 Aug 2024 17:48:43 +0200
Subject: [PATCH] doc: add note about shasum generation failure
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

PR-URL: https://github.com/nodejs/node/pull/54487
Reviewed-By: Ulises Gascón <ulisesgascongonzalez@gmail.com>
Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
---
 doc/contributing/releases.md | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md
index b1116de86f8599..0160d94fea5a61 100644
--- a/doc/contributing/releases.md
+++ b/doc/contributing/releases.md
@@ -944,6 +944,13 @@ a `NODEJS_RELEASE_HOST` environment variable:
 NODEJS_RELEASE_HOST=proxy.xyz ./tools/release.sh
 ```
 
+> \[!TIP]
+> Sometimes, due to machines being overloaded or other external factors,
+> the files at <https://nodejs.org/dist/index.json>, <https://nodejs.org/dist/index.tab>
+> or `SHASUMS256.txt` may not be generated correctly.
+> In this case you can repeat the signing step in order
+> to fix it. e.g: `./tools/release.sh -s`.
+
 `tools/release.sh` will perform the following actions when run:
 
 <details>