[cargo-smart-release]: reaching unreachable code if a section with only user generated content is expected to have generated content

[Byron]

The error:

thread 'main' panicked at 'internal error: entered unreachable code: BUG: User segments are never auto-generated', cargo-smart-release/src/changelog/merge.rs:100:49

Should be reproducible with

[…]
## Unreleased

### Features

* Shortcut links are now printed at the end of the stream like one would expect ([#33](https://github.com/Byron/pulldown-cmark-to-cmark/pull/33))
* email links are retained
* Now 422 of 649 common mark spec tests pass, up from 402.

Workaround: Rename ### Features to ### New Features, which isn't a known keyword.

Other side-effects: The lock files were not released despite that definitely happening and destruction and on signal. Signals are also initialized by default as far as I thought, but maybe that has to be revisited.

• The reason for this is panic = "abort", which won't run destructors nor will it trigger any signal handler. There might be a way to handle abort signals though.

[Byron]

This is fixed with v0.7.0