0
0
mirror of https://github.com/nodejs/node.git synced 2024-11-21 13:09:21 +01:00

doc: include git node release --promote to steps

Refs: https://github.com/nodejs/node-core-utils/pull/835
PR-URL: https://github.com/nodejs/node/pull/55835
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>
This commit is contained in:
Rafael Gonzaga 2024-11-19 15:15:34 -03:00 committed by GitHub
parent c921676512
commit 172841c2ef
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -707,12 +707,23 @@ the build before moving forward. Use the following list as a baseline:
### 11. Tag and sign the release commit
Once you have produced builds that you're happy with, create a new tag. By
waiting until this stage to create tags, you can discard a proposed release if
something goes wrong or additional commits are required. Once you have created a
tag and pushed it to GitHub, you _**must not**_ delete and re-tag. If you make
a mistake after tagging then you'll have to version-bump and start again and
count that tag/version as lost.
Once you have produced builds that you're happy with you can either run
`git node release --promote`
```bash
git node release -S --promote https://github.com/nodejs/node/pull/XXXX
```
to automate the remaining steps until step 16 or you can perform it manually
following the below steps.
***
Create a new tag: By waiting until this stage to create tags, you can discard
a proposed release if something goes wrong or additional commits are required.
Once you have created a tag and pushed it to GitHub, you _**must not**_ delete
and re-tag. If you make a mistake after tagging then you'll have to version-bump
and start again and count that tag/version as lost.
Tag summaries have a predictable format. Look at a recent tag to see: