Would it be possible to be a little more strict with changelog formatting?

[luzpaz]

Currently 1.2.1, 1.2.2 and 1.2.3 are consolidated. This makes it hard to remotely parse the changes that were made in the 2 minor versions after 1.2.1

ref: https://surge-synthesizer.github.io/changelog/

[baconpaul]

oooh the changelog is really not designed for parsing. What's your use case?

1.2.1 and 1.2.2 lasted order days or hours so we didn't break them out; but that was more for human consumption.

[luzpaz]

Usecase: http://freshcode.club/submit/surgext

But there are other downstream packagers that may be parsing changelogs as well.

[baconpaul]

Oh you should track our releases with tags not parsing the change log! We have signed git tags for each release and a distinct branch for each release which is atomic with the code changes

[mkruselj]

What Paul said.