This is already the case. That section will be added if you specify in your commit (see spec) that it introduces breaking changes.

Hi. In order to do this, you need to add an ! to the type in commit message like refactor!: change options interface. This will be automatically detected by changelogen to bump a major version + adding to the BREAKING CHANGES section.

I think would be nice if we add some little docs about semantic commits behavior in changelogen docs.

@pi0 It does add the commit into the Breaking changes section, but it doesn't provide the breaking change details if provided.

Like :

chore!: drop support for Node 6

BREAKING CHANGE: use JavaScript features not available in Node 6.

will generate:

⚠️ Breaking Changes

• ⚠️ drop support for Node 6 (beb780c3)

but use JavaScript features not available in Node 6. would not appear in the changelog. It seems unfortunate to mention that there's a breaking change if we couldn't provide any details about it.