Commit 091b4bf
committed
doc: add note about ssh key to releases
PR-URL: #31856
Reviewed-By: Myles Borins <myles.borins@gmail.com>
Reviewed-By: Beth Griggs <Bethany.Griggs@uk.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
Reviewed-By: James M Snell <jasnell@gmail.com>1 parent f858f23 commit 091b4bf
1 file changed
Lines changed: 24 additions & 2 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -553,8 +553,30 @@ formatting passes the lint rules on `master`. | |||
| 553 | 553 | to promote the builds as the `SHASUMS256.txt` file needs to be signed with the | |
| 554 | 554 | same GPG key!** | |
| 555 | 555 | ||
| 556 | - Use `tools/release.sh` to promote and sign the build. When run, it will perform | ||
| 557 | - the following actions: | ||
| 556 | + Use `tools/release.sh` to promote and sign the build. Before doing this, you'll | ||
| 557 | + need to ensure you've loaded the correct ssh key, or you'll see the following: | ||
| 558 | + | ||
| 559 | + ```sh | ||
| 560 | + # Checking for releases ... | ||
| 561 | + Enter passphrase for key '/Users/<user>/.ssh/id_rsa': | ||
| 562 | + dist@direct.nodejs.org's password: | ||
| 563 | + ``` | ||
| 564 | + | ||
| 565 | + The key can be loaded either with `ssh-add`: | ||
| 566 | + | ||
| 567 | + ```sh | ||
| 568 | + # Substitute node_id_rsa with whatever you've named the key | ||
| 569 | + $ ssh-add ~/.ssh/node_id_rsa | ||
| 570 | + ``` | ||
| 571 | + | ||
| 572 | + or at runtime with: | ||
| 573 | + | ||
| 574 | + ```sh | ||
| 575 | + # Substitute node_id_rsa with whatever you've named the key | ||
| 576 | + $ ./tools/release.sh -i ~/.ssh/node_id_rsa | ||
| 577 | + ``` | ||
| 578 | + | ||
| 579 | + `tools/release.sh` will perform the following actions when run: | ||
| 558 | 580 | ||
| 559 | 581 | **a.** Select a GPG key from your private keys. It will use a command similar | |
| 560 | 582 | to: `gpg --list-secret-keys` to list your keys. If you don't have any keys, it | |
0 commit comments