[dlundqvist]

We’ve been doing something similar at day job for a couple of years now, at least. Tried a few different things, but this cause us the fewest problems.

We have a monorepo with a dozen different products, supporting four rolling release series at any time. Some code is shared between products. So having a commit that contains the release note is very convenient. It’ll automatically follow merges, both when merging up bug fixes through all the release branches and merging in features.

When it’s time to build release notes, simply walk the new commits since last release and extract each release note.

Note, I’m leaving out most details on exactly how we have this setup. It’s not that complicated though.