You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/contributing/releases.md
+21-31Lines changed: 21 additions & 31 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,8 +30,8 @@ official release builds for Node.js, hosted on <https://nodejs.org/>.
30
30
*[14. Push the release tag](#14-push-the-release-tag)
31
31
*[15. Promote and sign the release builds](#15-promote-and-sign-the-release-builds)
32
32
*[16. Check the release](#16-check-the-release)
33
-
*[17. Create a blog post](#17-create-a-blog-post)
34
-
*[18. Create the release on GitHub](#18-create-the-release-on-github)
33
+
*[17. Create the release on GitHub](#17-create-the-release-on-github)
34
+
*[18. Create a blog post](#18-create-a-blog-post)
35
35
*[19. Announce](#19-announce)
36
36
*[20. Celebrate](#20-celebrate)
37
37
*[LTS releases](#lts-releases)
@@ -1047,21 +1047,31 @@ have the right internal version strings. Check that the API docs are available
1047
1047
at <https://nodejs.org/api/>. Check that the release catalog files are correct
1048
1048
at <https://nodejs.org/dist/index.tab> and <https://nodejs.org/dist/index.json>.
1049
1049
1050
-
### 17. Create a blog post
1050
+
### 17. Create the release on GitHub
1051
+
1052
+
* Go to the [New release page](https://github.com/nodejs/node/releases/new).
1053
+
* Select the tag version you pushed earlier.
1054
+
* For release title, copy the title from the changelog.
1055
+
* For the description, copy the rest of the changelog entry.
1056
+
* If you are not releasing the latest "Current", uncheck
1057
+
"Set as the latest release".
1058
+
* Click on the "Publish release" button.
1059
+
1060
+
### 18. Create a blog post
1051
1061
1052
1062
There is an automatic build that is kicked off when you promote new builds, so
1053
1063
within a few minutes nodejs.org will be listing your new version as the latest
1054
-
release. However, the blog post is not yet fully automatic.
1064
+
release, and a blog post draft PR will be created.
1055
1065
1056
-
Create a new blog post by running the [nodejs.org release-post.js script][]:
1066
+
In the event that a draft PR _is not created_, the [`scripts:release-post`][] script
This script will use the promoted builds and changelog to generate the post. Run
1063
-
`npm run serve` to preview the post locally before pushing to the
1064
-
[nodejs.org repository][].
1074
+
This script will use the promoted builds and changelog to generate the post.
1065
1075
1066
1076
* You can add a short blurb just under the main heading if you want to say
1067
1077
something important, otherwise the text should be publication ready.
@@ -1076,33 +1086,13 @@ This script will use the promoted builds and changelog to generate the post. Run
1076
1086
to reflect those changes.
1077
1087
1078
1088
* Always use pull-requests on the [nodejs.org repository][]. Be respectful
1079
-
of the website team, but you do not have to wait for PR sign-off. Please
1080
-
use the following commit message format:
1081
-
1082
-
```console
1083
-
Blog: vX.Y.Z release post
1084
-
1085
-
Refs: <full URL to your release proposal PR>
1086
-
```
1087
-
1088
-
* In order to trigger the CI Checks of the [nodejs.org repository][]; Please
1089
-
attach the `github_actions:pull-request` label to the PR.
1089
+
of the website team, but you do not have to wait for PR sign-off.
1090
1090
1091
1091
* Changes to the base branch, `main`, on the [nodejs.org repository][] will
1092
1092
trigger a new build of nodejs.org, so your changes should appear a few minutes
1093
1093
after pushing. You can follow the [Deployments](https://github.com/nodejs/nodejs.org/deployments) page
1094
1094
to see when the build finishes and gets published.
1095
1095
1096
-
### 18. Create the release on GitHub
1097
-
1098
-
* Go to the [New release page](https://github.com/nodejs/node/releases/new).
1099
-
* Select the tag version you pushed earlier.
1100
-
* For release title, copy the title from the changelog.
1101
-
* For the description, copy the rest of the changelog entry.
1102
-
* If you are not releasing the latest "Current", uncheck
1103
-
"Set as the latest release".
1104
-
* Click on the "Publish release" button.
1105
-
1106
1096
### 19. Announce
1107
1097
1108
1098
The nodejs.org website will automatically rebuild and include the new version.
@@ -1469,7 +1459,7 @@ Typical resolution: sign the release again.
0 commit comments