Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fixup!
  • Loading branch information
avivkeller committed Oct 22, 2025
commit 1b1a358507feff5ad2b696837d0f5bd28fc760e7
40 changes: 34 additions & 6 deletions doc/contributing/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ official release builds for Node.js, hosted on <https://nodejs.org/>.
* [15. Promote and sign the release builds](#15-promote-and-sign-the-release-builds)
* [16. Check the release](#16-check-the-release)
* [17. Create the release on GitHub](#17-create-the-release-on-github)
* [17.1 Merge the blog post](#171-merge-the-blog-post)
* [18. Create a blog post](#18-create-a-blog-post)
* [19. Announce](#19-announce)
* [20. Celebrate](#20-celebrate)
* [LTS releases](#lts-releases)
Expand Down Expand Up @@ -1079,12 +1079,40 @@ at <https://nodejs.org/dist/index.tab> and <https://nodejs.org/dist/index.json>.
"Set as the latest release".
* Click on the "Publish release" button.

#### 17.1 Merge the Blog Post
### 18. Create a blog post

Once a release is created, an automation will open a PR in the [nodejs.org repository][]
to create a blog post. 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. Be respectful
of the website team, but you do not have to wait for PR sign-off.
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, and a blog post draft PR will be created.

In the event that a draft PR _is not created_, the following script can be used
as an alternative:

```bash
node ./apps/site/scripts/release-post/index.mjs x.y.z
```

This script will use the promoted builds and changelog to generate the post.

* 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.

* The `SHASUMS256.txt.asc` content is at the bottom of the post. When you update
the list of tarballs you'll need to copy/paste the new contents of this file
to reflect those changes.

* Always use pull-requests on the [nodejs.org repository][]. Be respectful
of the website team, but you do not have to wait for PR sign-off.

* Changes to the base branch, `main`, on the [nodejs.org repository][] will
trigger a new build of nodejs.org, so your changes should appear a few minutes
after pushing. You can follow the [Deployments](https://github.com/nodejs/nodejs.org/deployments) page
to see when the build finishes and gets published.

### 19. Announce

Expand Down
Loading