Release draft

A release draft gathers the pull requests merged into a repository’s default branch since its latest release, sorts them into sections by label, and suggests the next version.

Settings

Setting	Stored as	Accepts	Default
Title (named after the repository if empty)	`title`	Text, at most 120	empty
Forge (only shown when the board has more than one)	`host`	Text, at least 1 character and at most 253	`github.com`
Repository	`repo`	Text, at most 200	empty
Sections, by label	`sections`	1 to 12 sections, each a title (up to 60 characters) and up to 20 labels. A section with no labels takes everything else	5 items (below)
Leave out pull requests labelled	`skip`	Up to 20 labels	`skip-changelog`, `no-release-notes`, `dependencies`
Thank contributors	`contributors`	On or off	on

The default sections are:

Section	Labels
Breaking changes	`breaking`, `breaking change`, `semver-major`
Features	`enhancement`, `feature`, `feat`
Fixes	`bug`, `fix`, `bugfix`
Docs	`docs`, `documentation`
Other	everything else

A pull request goes in the first section with one of its labels. Reset puts the default sections back.

Using it

The header says which release it’s since (“since v5.3.0 · 23 d ago”, or “No releases yet: everything merged so far”), and the next version: v5.3.0 → v5.4.0, with “Breaking”, “New features” or “Fixes only”.

The bump is major if anything is labelled breaking (or semver-major, or major), minor for features, and patch otherwise. Before 1.0, a breaking change bumps the minor version.
Preview notes shows the notes as Markdown, and Copy notes copies them: a “What’s changed” heading, a section for each group with “- Title (#123) by @author”, the contributors (“Thanks to @a, @b and @c.”, leaving out bots), and a full changelog link comparing the tags.
It reads up to 50 pull requests merged since the release, the most recently updated first.

Rows drag out onto the board as cards.