From 1127d7e3fa2546241d524a9fe7c3605add62e052 Mon Sep 17 00:00:00 2001 From: Gregory Schier Date: Wed, 11 Feb 2026 17:38:13 -0800 Subject: [PATCH] Use consistent release title format in generate-release-notes command --- .claude/commands/release/generate-release-notes.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/.claude/commands/release/generate-release-notes.md b/.claude/commands/release/generate-release-notes.md index 2ca790b5..6a42ea32 100644 --- a/.claude/commands/release/generate-release-notes.md +++ b/.claude/commands/release/generate-release-notes.md @@ -43,5 +43,7 @@ The skill generates markdown-formatted release notes following this structure: After outputting the release notes, ask the user if they would like to create a draft GitHub release with these notes. If they confirm, create the release using: ```bash -gh release create --draft --prerelease --title "" --notes '' +gh release create --draft --prerelease --title "Release " --notes '' ``` + +**IMPORTANT**: The release title format is "Release XXXX" where XXXX is the version WITHOUT the `v` prefix. For example, tag `v2026.2.1-beta.1` gets title "Release 2026.2.1-beta.1".