Skip to content

Commit 87dfed0

Browse files
danielleadamsMylesBorins
authored andcommitted
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]>
1 parent 1758ac8 commit 87dfed0

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

doc/guides/releases.md

+8-2
Original file line numberDiff line numberDiff line change
@@ -92,8 +92,14 @@ signed by someone who has been authorized to create a release.
9292

9393
The GPG keys should be fetchable from a known third-party keyserver. The SKS
9494
Keyservers at <https://sks-keyservers.net> are recommended. Use the
95-
[submission](https://pgp.mit.edu/) form to submit a new GPG key. Keys should be
96-
fetchable via:
95+
[submission](https://pgp.mit.edu/) form to submit a new GPG key. You'll need to
96+
do an ASCII-armored export of your key first:
97+
98+
```console
99+
$ gpg --armor --export [email protected] > ~/nodekey.asc
100+
```
101+
102+
Keys should be fetchable via:
97103

98104
```console
99105
$ gpg --keyserver pool.sks-keyservers.net --recv-keys <FINGERPRINT>

0 commit comments

Comments
 (0)