Writing changesets with headings results in unexpected heading structure

Affected Packages

apply-release-plan

Problem

When writing a changset and you want to separate different parts of the change you can use headings, so for example:

## Summary

words

## Migration strategies

words

And so on. Unfortunately in the context of the wider CHANGELOG these headers now are no longer under their appropriate major minor patch heading, which kind of sucks! You can see an example here https://bitbucket.org/atlassian/atlassian-frontend-mirror/src/master/design-system/button/CHANGELOG.md, sometimes even a h2 is used which also breaks versions! Not great.

Proposed solution

I see two paths.

1. Re-write headings so they make sense underneath ### Major and so on.
2. Block headings altogether from changesets

[emmatown]

Sure but let’s say a changeset has an h4 in the summary, should it be changed? should it stay the same? should h4-6 be banned? should h1-3 be banned instead? There will be different opinions on these and apply-release-plan should shouldn’t have to have opinions on it.

Also, there have been vague thoughts that changelog generators should be able to change stuff like those headings.

[emmatown]

I’m fine with the first path as long as this is only a thing in the changelog generators(i.e. not apply-release-plan but cli/changelog, changelog-git and changelog-github)