Skip to content

fix(skills): start tag annotation with blank line when no custom title#1239

Open
rh-hemartin wants to merge 1 commit into
mainfrom
fix/1237-cutting-releases-blank-first-line
Open

fix(skills): start tag annotation with blank line when no custom title#1239
rh-hemartin wants to merge 1 commit into
mainfrom
fix/1237-cutting-releases-blank-first-line

Conversation

@rh-hemartin
Copy link
Copy Markdown
Contributor

Summary

  • GoReleaser reads the first non-empty annotation line as .TagSubject, causing verbose release titles (e.g. v0.9.0: Features - Docs sidebar search filter…) when no custom title is given
  • Updates step 6 of the cutting-releases skill to require a blank first line instead of "start the body directly with highlights"

Closes #1237

Test plan

  • Cut a release with no custom title — verify release title is just the tag (e.g. v0.9.0)
  • Cut a release with a custom title — verify title renders as vX.Y.Z: Custom Title

🤖 Generated with Claude Code

GoReleaser reads the first non-empty annotation line as .TagSubject,
so starting directly with a category header produces verbose titles
like "v0.9.0: Features - ...". A leading blank line yields an empty
.TagSubject and a clean "v0.9.0" title.

Closes #1237

Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
@github-actions
Copy link
Copy Markdown

Site preview

Preview: https://8d0a8124-site.fullsend-ai.workers.dev

Commit: 98531511e3d1303302db5622c918c505fafc3be0

@fullsend-ai-review
Copy link
Copy Markdown

Review

Findings

No findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-merge All reviewers approved — ready to merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cutting-releases skill produces verbose release titles when no custom title is given

1 participant