From 4865cac0f500ef188f260ba4ee80197bc21fd103 Mon Sep 17 00:00:00 2001 From: Rafael Gonzaga Date: Sun, 12 May 2024 14:20:51 -0300 Subject: [PATCH] doc: mention push.followTags config MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit This has happened in v20.13.0 release. Adding this doc to prevent edge cases where the releaser will sign and push but won't be able to promote the release. PR-URL: https://github.com/nodejs/node/pull/52906 Reviewed-By: Ulises Gascón Reviewed-By: Paolo Insogna Reviewed-By: Marco Ippolito Reviewed-By: Antoine du Hamel --- doc/contributing/releases.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/doc/contributing/releases.md b/doc/contributing/releases.md index 0dab193f1aaf08..9fd8d51fa071a0 100644 --- a/doc/contributing/releases.md +++ b/doc/contributing/releases.md @@ -726,7 +726,17 @@ Install `git-secure-tag` npm module: npm install -g git-secure-tag ``` -Create a tag using the following command: +> Ensure to disable `--follow-tags` in your git settings using: `git config push.followTags false` + +If your private key is protected by a passphrase, you might need to run: + +```bash +export GPG_TTY=$(tty) +``` + +before creating the tag. + +To create a tag use the following command: ```bash git secure-tag -sm "YYYY-MM-DD Node.js vx.y.z () Release"