-
Notifications
You must be signed in to change notification settings - Fork 29.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: mention tools/release -a option #56124
doc: mention tools/release -a option #56124
Conversation
Review requested:
|
@@ -966,6 +966,13 @@ a `NODEJS_RELEASE_HOST` environment variable: | |||
NODEJS_RELEASE_HOST=proxy.xyz ./tools/release.sh | |||
``` | |||
|
|||
In case `gpg` is unable to autoselect a key, you can retry using the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How can we do it with git node release prepare?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as far as I can tell, based on today's run, git node release promote default behavior will just stop and ask you to run it in a separate shell, like this:
✔ Ready to continue? yes
ℹ You are running in dry-run mode, meaning NCU will not run the `git push` commands, you would need to copy-paste the following command in another terminal window. Alternatively, pass `--run` flag to ask NCU to run the command for you (might not work if you need to type a passphrase to push to the remote).
ℹ Run the following command to sign and promote the release:
ℹ ./tools/release.sh -i <keyPath>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe the autodetect feature needs to be 100% in case you want to run it in --run
mode, otherwise we should put extra validation along the way to catch it early on in case values like these are unable to be retrieved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That makes sense
Document that running `./tools/release.sh` script using the recently added `-a` CLI flag enables the previously-default interactive interface to select the correct PGP key.
d9e0f4f
to
0a1dcae
Compare
Landed in 660d533 |
Document that running `./tools/release.sh` script using the recently added `-a` CLI flag enables the previously-default interactive interface to select the correct PGP key. PR-URL: #56124 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Document that running `./tools/release.sh` script using the recently added `-a` CLI flag enables the previously-default interactive interface to select the correct PGP key. PR-URL: #56124 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Document that running `./tools/release.sh` script using the recently added `-a` CLI flag enables the previously-default interactive interface to select the correct PGP key. PR-URL: #56124 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Document that running `./tools/release.sh` script using the recently added `-a` CLI flag enables the previously-default interactive interface to select the correct PGP key. PR-URL: #56124 Reviewed-By: Rafael Gonzaga <[email protected]> Reviewed-By: Antoine du Hamel <[email protected]> Reviewed-By: Richard Lau <[email protected]>
Mention that running
./tools/release.sh
script using the recently added-a
option enables the previously-default interactive interface to select the correct GPG key.