Release Notes - auto generation/capture

[planetf1]

In review comments on #1302 there was a minor breaking change identified. The suggestion was to capture in release notes.

However there is no mechanism to do this. Options might include

• markers added in PR text & auto-injected into release notes
• per-release ongoing doc (manually edited)
• raising an issue with certain labels (release owner writes up notes)

Seems like a discussion worth having especially around deprecations and changes of behaviour

[psschwei]

I'm in favor of flagging breaking changes.

We could update the PR label action to add a "breaking changes" label when there is a cc-style ! in the commit. That would group all breaking changes together.

[psschwei]

I also like the idea of including a note for breaking changes in the PR and then having automation assemble it into the release notes when those are created.

That could look something like this:

A step in release.sh (or a small script it calls) that, between picking START_TAG and creating the release:

1. Enumerate merged PRs in the range — list commits START_TAG..HEAD, map each to its PR. gh pr list --search or gh api per merge commit. (You
   already compute START_TAG at release.sh:66–84, so the range is in hand.)
2. Pull each PR body — gh pr view --json body.
3. Extract the fenced block — regex out release-note … from each body. Skip empty / NONE blocks
4. Assemble — concatenate into a "Breaking Changes / Migration" section.
5. Inject — write to a temp file and pass via --notes-file, combined with --generate-notes so you keep the auto-generated PR list underneath.