GeezerVison is showing github.com — doc: add more lts update steps to release guide · nodejs/node@3381a17
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/contributing/releases.md +19Lines changed: 19 additions & 0 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -1034,6 +1034,25 @@ existing labels for that release line, such as `vN.x`. |
1034 | 1034 | If the release is transitioning from Active LTS to Maintenance, the |
1035 | 1035 | `backport-requested-vN.x` label must be deleted. |
1036 | 1036 |
|
| 1037 | +### Add new codename to nodejs-latest-linker |
| 1038 | + |
| 1039 | +In order to make sure a download URL |
| 1040 | +(e.g: <https://nodejs.org/download/release/latest-codename/>) will be available |
| 1041 | +for the new LTS release line you need to submit a PR to |
| 1042 | +<https://github.com/nodejs/nodejs-latest-linker> and add a new entry for the |
| 1043 | +new LTS codename in its `ltsNames` map located in the `./latest-linker.js` |
| 1044 | +file. |
| 1045 | + |
| 1046 | +Make sure to reach out to the Build WG in order to validate that the new URL is |
| 1047 | +available as part of the LTS release promotion. |
| 1048 | + |
| 1049 | +### Update Release repo info |
| 1050 | + |
| 1051 | +Add the new LTS codename to the release schedule table located in the |
| 1052 | +`./README.md` file located at the <https://github.com/nodejs/Release> |
| 1053 | +repository along with the addition of the new codename to the `./schedule.json` |
| 1054 | +file in that same repo. |
| 1055 | + |
1037 | 1056 | ## Major releases |
1038 | 1057 |
|
1039 | 1058 | The process for cutting a new Node.js major release has a number of differences |
|