Skip to content

docs(releasing): document release-note generation in 'Cutting a release'#173

Merged
edwin-zvs merged 1 commit into
mainfrom
releasing-notes
May 23, 2026
Merged

docs(releasing): document release-note generation in 'Cutting a release'#173
edwin-zvs merged 1 commit into
mainfrom
releasing-notes

Conversation

@edwin-zvs

Copy link
Copy Markdown
Contributor

The release workflow already auto-generates the GitHub Release body (it passes generate_release_notes: true), but the Cutting a release steps in docs/RELEASING.md never said so. This documents it.

Adds a step 4, "Review the release notes", covering:

  • The body is filled automatically from the PRs merged since the previous v* tag (categorized changelog + contributor credits + Full Changelog link).
  • PR titles become the changelog → keep titles clear/conventional; this is also why we squash-merge (one tidy line per change).
  • You can edit the body after publishing (add highlights, breaking-change callouts, upgrade notes).
  • How to group notes into sections via a .github/release.yml — no workflow change needed.

Also tweaks the intro line to mention the release is published "with auto-generated release notes". Docs-only.

🤖 Generated with Claude Code

…release'

The release workflow already passes generate_release_notes: true, but the
'Cutting a release' steps didn't mention it. Add a step explaining that the
release body is filled from merged PR titles since the previous tag (hence
clean, conventional titles + squash-merge), that it can be edited after
publishing, and how to categorize notes via .github/release.yml.
@edwin-zvs
edwin-zvs merged commit ea44b33 into main May 23, 2026
1 check passed
@edwin-zvs
edwin-zvs deleted the releasing-notes branch May 23, 2026 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant