doc: add gpg key export directions to releases doc

Adds an extra step with instructions for exporting a gpg key to be uploaded to the key server. PR-URL: #35298 Reviewed-By: Richard Lau <[email protected]> Reviewed-By: Beth Griggs <[email protected]> Reviewed-By: Rich Trott <[email protected]>
nodejs · Sep 29, 2020 · 87dfed0 · 87dfed0
1 parent 1758ac8
commit 87dfed0
Showing 1 changed file with 8 additions and 2 deletions.
diff --git a/doc/guides/releases.md b/doc/guides/releases.md
@@ -92,8 +92,14 @@ signed by someone who has been authorized to create a release.
 
 The GPG keys should be fetchable from a known third-party keyserver. The SKS
 Keyservers at <https://sks-keyservers.net> are recommended. Use the
-[submission](https://pgp.mit.edu/) form to submit a new GPG key. Keys should be
-fetchable via:
+[submission](https://pgp.mit.edu/) form to submit a new GPG key. You'll need to
+do an ASCII-armored export of your key first:
+
+```console
+$ gpg --armor --export [email protected] > ~/nodekey.asc
+```
+
+Keys should be fetchable via:
 
 ```console
 $ gpg --keyserver pool.sks-keyservers.net --recv-keys <FINGERPRINT>