Skip to content

Commit 8e790b7

Browse files
Fishrock123evanlucas
authored andcommitted
doc: add instructions to only sign a release
PR-URL: #5876 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
1 parent f1f9aff commit 8e790b7

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

doc/releases.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -246,6 +246,8 @@ Use `tools/release.sh` to promote and sign the build. When run, it will perform
246246

247247
If you didn't wait for ARM builds in the previous step before promoting the release, you should re-run `tools/release.sh` after the ARM builds have finished. That will move the ARM artifacts into the correct location. You will be prompted to re-sign SHASUMS256.txt.
248248

249+
Note: it is possible to only sign a release by running `./tools/release.sh -s vX.Y.Z`.
250+
249251
### 13. Check the Release
250252

251253
Your release should be available at <https://nodejs.org/dist/vx.y.z/> and <https://nodejs.org/dist/latest/>. Check that the appropriate files are in place. You may want to check that the binaries are working as appropriate and have the right internal version strings. Check that the API docs are available at <https://nodejs.org/api/>. Check that the release catalog files are correct at <https://nodejs.org/dist/index.tab> and <https://nodejs.org/dist/index.json>.

0 commit comments

Comments
 (0)