Skip to content

Commit

Permalink
doc: add instructions to only sign a release
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
Fishrock123 authored and Myles Borins committed Mar 30, 2016
1 parent 55c3f80 commit 60ddab8
Showing 1 changed file with 2 additions and 0 deletions.
2 changes: 2 additions & 0 deletions doc/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -246,6 +246,8 @@ Use `tools/release.sh` to promote and sign the build. When run, it will perform

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.

Note: it is possible to only sign a release by running `./tools/release.sh -s vX.Y.Z`.

### 13. Check the Release

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>.
Expand Down

0 comments on commit 60ddab8

Please sign in to comment.