diff options
author | Myles Borins <mborins@us.ibm.com> | 2016-01-13 03:07:29 +0300 |
---|---|---|
committer | James M Snell <jasnell@gmail.com> | 2016-01-13 19:11:40 +0300 |
commit | 65825b79aa0c99a7873e58002d21a1923441d2ca (patch) | |
tree | fcf1ef708e08ff2873ab666704d3fab22e401f96 /doc/releases.md | |
parent | d755432fa9bdd5fadd98dfac4ac4b6f5329cc8b4 (diff) |
docs: fix npm command in releases.md
PR-URL: https://github.com/nodejs/node/pull/4656
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Rod Vagg <rod@vagg.org>
Reviewed-By: James M Snell <jasnell@gmail.com>
Diffstat (limited to 'doc/releases.md')
-rw-r--r-- | doc/releases.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/releases.md b/doc/releases.md index 2f55c2d8188..daa325b0bce 100644 --- a/doc/releases.md +++ b/doc/releases.md @@ -254,7 +254,7 @@ Your release should be available at <https://nodejs.org/dist/vx.y.z/> and <https There is an automatic build that is kicked off when you promote new builds, so within a few minutes nodejs.org will be listing your new version as the latest release. However, the blog post is not yet fully automatic. -Create a new blog post by running the [nodejs.org release-post.js script](https://github.com/nodejs/nodejs.org/blob/master/scripts/release-post.js). This script will use the promoted builds and changelog to generate the post. Run `npm serve` to preview the post locally before pushing to the [nodejs.org](https://github.com/nodejs/nodejs.org) repo. +Create a new blog post by running the [nodejs.org release-post.js script](https://github.com/nodejs/nodejs.org/blob/master/scripts/release-post.js). This script will use the promoted builds and changelog to generate the post. Run `npm run serve` to preview the post locally before pushing to the [nodejs.org](https://github.com/nodejs/nodejs.org) repo. * You can add a short blurb just under the main heading if you want to say something important, otherwise the text should be publication ready. * The links to the download files won't be complete unless you waited for the ARMv6 builds. Any downloads that are missing will have `*Coming soon*` next to them. It's your responsibility to manually update these later when you have the outstanding builds. |