From 22e2e34724caf4b3df75619e1b6b81b74e57d465 Mon Sep 17 00:00:00 2001 From: rob thijssen Date: Thu, 16 Apr 2026 15:23:19 +0300 Subject: [PATCH] docs: note tag.gpgsign requires -m flag on tag creation MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Learned the hard way on the v1.0.0 release — this repo inherits tag.gpgsign=true from global config, so `git tag v1.0.0` fails with "no tag message?" rather than creating a lightweight tag. Update the release recipe to use -m explicitly. Co-Authored-By: Claude Opus 4.6 (1M context) --- CLAUDE.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/CLAUDE.md b/CLAUDE.md index f4e7851..466c058 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -32,12 +32,14 @@ major-version tag and an immutable semver tag. 2. Determine the next version by bumping the patch or minor from the latest semver tag (e.g. `v1.0.3` → `v1.0.4` for a fix, `v1.1.0` for a non-breaking feature). -3. Tag and push. Both the immutable semver tag and the moving major - tag get pushed in the same command: +3. Tag and push. This repo has `tag.gpgsign=true` globally, so tags + must be annotated with a message (`-m`) and a GPG key must be + available. Both the immutable semver tag and the moving major tag + get pushed in the same release: ```sh - git tag v1.0.4 - git tag -f v1 + git tag -m "v1.0.4" v1.0.4 + git tag -f -m "v1 - track latest v1.x.y" v1 git push origin main git push origin v1.0.4 git push origin v1 --force @@ -53,8 +55,8 @@ major-version tag and an immutable semver tag. 2. Cut a new major tag (`v2.0.0`) and a new major-line tag (`v2`): ```sh - git tag v2.0.0 - git tag v2 + git tag -m "v2.0.0" v2.0.0 + git tag -m "v2 - track latest v2.x.y" v2 git push origin main v2.0.0 v2 ```