Commit 3e6b3a9
doc: include git node release --promote to steps
Refs: nodejs/node-core-utils#835
PR-URL: #55835
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Joyee Cheung <joyeec9h3@gmail.com>1 parent 8ff082c commit 3e6b3a9
1 file changed
Lines changed: 17 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -707,12 +707,23 @@ the build before moving forward. Use the following list as a baseline: | |||
| 707 | 707 | ||
| 708 | 708 | ### 11. Tag and sign the release commit | |
| 709 | 709 | ||
| 710 | - Once you have produced builds that you're happy with, create a new tag. By | ||
| 711 | - waiting until this stage to create tags, you can discard a proposed release if | ||
| 712 | - something goes wrong or additional commits are required. Once you have created a | ||
| 713 | - tag and pushed it to GitHub, you _**must not**_ delete and re-tag. If you make | ||
| 714 | - a mistake after tagging then you'll have to version-bump and start again and | ||
| 715 | - count that tag/version as lost. | ||
| 710 | + Once you have produced builds that you're happy with you can either run | ||
| 711 | + `git node release --promote` | ||
| 712 | + | ||
| 713 | + ```bash | ||
| 714 | + git node release -S --promote https://github.com/nodejs/node/pull/XXXX | ||
| 715 | + ``` | ||
| 716 | + | ||
| 717 | + to automate the remaining steps until step 16 or you can perform it manually | ||
| 718 | + following the below steps. | ||
| 719 | + | ||
| 720 | + *** | ||
| 721 | + | ||
| 722 | + Create a new tag: By waiting until this stage to create tags, you can discard | ||
| 723 | + a proposed release if something goes wrong or additional commits are required. | ||
| 724 | + Once you have created a tag and pushed it to GitHub, you _**must not**_ delete | ||
| 725 | + and re-tag. If you make a mistake after tagging then you'll have to version-bump | ||
| 726 | + and start again and count that tag/version as lost. | ||
| 716 | 727 | ||
| 717 | 728 | Tag summaries have a predictable format. Look at a recent tag to see: | |
| 718 | 729 | ||
0 commit comments