Skip to content

Commit

Permalink
doc: mention push.followTags config
Browse files Browse the repository at this point in the history
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: #52906
Reviewed-By: Ulises Gascón <[email protected]>
Reviewed-By: Paolo Insogna <[email protected]>
Reviewed-By: Marco Ippolito <[email protected]>
Reviewed-By: Antoine du Hamel <[email protected]>
  • Loading branch information
RafaelGSS authored and marco-ippolito committed Jun 17, 2024
1 parent 7603a51 commit be309bd
Showing 1 changed file with 11 additions and 1 deletion.
12 changes: 11 additions & 1 deletion doc/contributing/releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -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 <vx.y.z> <commit-sha> -sm "YYYY-MM-DD Node.js vx.y.z (<release-type>) Release"
Expand Down

0 comments on commit be309bd

Please sign in to comment.