This package produces CHANGELOG.md files that are incompatible with markdownlint.

The written changelog conforms exactly to the example from the Keep a Changelog website, but are its spacing conventions really relevant to the spec our our ability to parse a changelog?

I believe that the spacing is irrelevant to the Keep a Changelog spec, and we should make the output changelogs compatible with markdownlint at least in terms of spacing. There may even be an argument to integrate markdownlint into this tool, but that's a different question.

Related: #50. markdownlint-compatibility appears to be largely equivalent with Prettier-compatibility.