ci: group the generated release notes by category

[dims]

Problem

release.yml already sets generate_release_notes: true, so GitHub lists every merged pull request. It lists them flat. A dependency bump reads the same as a bug fix, and a reader has to scan the whole list to find what changed for them.

Change

.github/release.yml, 38 lines with comments. GitHub groups the list it already generates. No change to how a release is cut, no new tooling, no new workflow.

Sections: New Features, Bug Fixes, Documentation, Dependency Updates, Other Changes.

The limitation, stated up front

Categories match on pull request labels. That is the only thing GitHub's generator can match on — it cannot read a commit or title prefix, so the Conventional Commit prefixes this project already uses do not help here.

Most human pull requests carry no labels today, so they land in Other Changes. That is exactly where they land now, so nothing gets worse, and labelling a pull request starts paying immediately.

Two sections work from day one: Dependency Updates, because Dependabot applies the dependencies label itself, and Other Changes.

Why dependency bumps are grouped rather than excluded

The obvious move is to drop them from the notes entirely, which is what aicr does via GoReleaser's changelog filters. I did not, because a consumer deciding whether to upgrade wants to see them. The problem was never that dependency bumps are published — it was that they were interleaved with everything else. A section at the bottom fixes that without hiding information.

Verification

• Parses, and every key checked against the documented schema (changelog.exclude.{labels,authors}, changelog.categories[].{title,labels,exclude}).
• All four referenced labels — enhancement, bug, documentation, dependencies — already exist in the repository.
• The "*" catch-all is last, so it only claims what nothing above matched.
• make verify passes.

Possible follow-up

If you want the categories to fill themselves, a small workflow could apply enhancement, bug or documentation from the Conventional Commit prefix already in the pull request title. Titles are consistent enough for it — the last 20 merged pull requests break down as 6 fix, 4 build, 4 docs, 2 chore, 2 feat, 1 ci, 1 test. Not included here because it is a separate change with its own trade-offs.

[ndipebot]

nit