From 7b32e0eeb08391db1aef1fd4d811b458e082c526 Mon Sep 17 00:00:00 2001 From: RafaelGSS Date: Tue, 11 Apr 2023 18:15:21 -0300 Subject: [PATCH] doc: fix release-post script location --- doc/contributing/releases.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index 9c2d54ba1b4137..f86555bcfd26c9 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -954,7 +954,12 @@ 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][]. +Create a new blog post by running the [nodejs.org release-post.js script][]: + +```console +$ node ./scripts/release-post/index.mjs x.y.z ✱ +``` + 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 repository][]. @@ -1287,5 +1292,5 @@ take place once a new LTS line has been released. [Snap]: https://snapcraft.io/node [build-infra team]: https://github.com/orgs/nodejs/teams/build-infra [expected assets]: https://github.com/nodejs/build/tree/HEAD/ansible/www-standalone/tools/promote/expected_assets -[nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/scripts/release-post.js +[nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/scripts/release-post/index.mjs [nodejs.org repository]: https://github.com/nodejs/nodejs.org