doc: fix release guide example consistency

This changeset fixes two consistency issues in this single example that
guides releasers on how to push the tag to the remote repo.

The first issue is that the remote git reference is consistently
referred as `upstream` elsewhere in the guide.

The second issue being that the version example used in the rest of the
guide should be a fictional `v1.2.3` as stated in the "How to create a
release" guide notes:

>  * Examples will use the fictional release version `1.2.3`.

PR-URL: https://github.com/nodejs/node/pull/44385
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Richard Lau <rlau@redhat.com>
Reviewed-By: Rafael Gonzaga <rafael.nunu@hotmail.com>
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
pull/44418/head
Ruy Adorno 2022-08-27 05:54:40 -04:00 committed by GitHub
parent ee75ad7a38
commit 5a40b074ab
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions

View File

@ -737,7 +737,7 @@ haven't pushed your tag first, then build promotion won't work properly.
Push the tag using the following command:
```console
$ git push <remote> <vx.y.z>
$ git push upstream v1.2.3
```
_Note_: Please do not push the tag unless you are ready to complete the