Multiline bodys

[davidolrik]

I've discovered a small bug / missing feature when adding multiline change fragments.

Given these two changes:

kind: Build
body: |
  Line 1
  Line 2
time: 2025-10-10T11:54:26.89874+02:00

kind: Build
body: Single line
time: 2025-10-10T15:27:25.397089+02:00

I get this markdown:

## v0.42.0 - 2025-10-10

### Build

- Line 1
Line 2


- Single line

Only the first line is prefixed with a dash and there a a two extra newlines that shouldn't be there.

Removing the extra newlines, and indenting the rest of the body and adding two spaces to the end of each line should be all that is needed to fix this without changing too much or adding direct for sub changes or something like that.

## v0.42.0 - 2025-10-10

### Build

- Line 1  
  Line 2  
- Single line

What do you think?

[miniscruff]

What does your config look like?

[davidolrik]

Yes, that fixes it when I do changie merge, but I want it to be fixed when I do changie batch.

I have this newline config now:

newlines:
    beforeChangelogVersion: 1
    afterChangelogVersion: 1
    beforeKind: 1
    afterKind: 1

And that makes my CHANGELOG.md valid markdown, but the intermediary version files are not, because they lack the final newline.

So what I'm looking for is having afterChangelogVersion: 0 and a new option which is applied on changie batch that ensures the intermediary version files always end with exactly one newline.

[miniscruff]

oh I see. I don't believe I have a config for that, I don't tend to use the intermediary files so a config for that wasn't on my mind.
Maybe adding an "afterReleaseNotes" to the newlines config would be necessary.

[davidolrik]

afterReleaseNotes sounds like a good idea!

[miniscruff]

#831 was the code, thanks for the help