summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJeremiah Senkpiel <fishrock123@rocketmail.com>2016-03-23 14:47:12 -0400
committerMyles Borins <mborins@us.ibm.com>2016-03-30 13:14:17 -0700
commit60ddab841ea706cb3ab5db250466a9f5bcd8710d (patch)
tree64eec183e7e3f1dbbdabff2998ee46d6d4fe7d6e /doc
parent55c3f804c4a077873a438846931fd0fcea0caba2 (diff)
downloadnodejs-60ddab841ea706cb3ab5db250466a9f5bcd8710d.tar.gz
nodejs-60ddab841ea706cb3ab5db250466a9f5bcd8710d.tar.bz2
nodejs-60ddab841ea706cb3ab5db250466a9f5bcd8710d.zip
doc: add instructions to only sign a release
PR-URL: https://github.com/nodejs/node/pull/5876 Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/releases.md2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/releases.md b/doc/releases.md
index 1c77b91a0..512deb34a 100644
--- a/doc/releases.md
+++ b/doc/releases.md
@@ -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>.