fix issue with changelog for release

[nmerget]

the changelog action works for prereleases, but the normal release changelog would be empty.

Can this be configured in conventional-changelog-cli?

[dkolba]

I was not familiar with the automatic changelog generation GitHub provides when publishing a Release/Pre-Release when I implemented the feature. Do we need a custom changelog at all? I'd suggest to use the provided GitHub functionality and axe the changelog step in CI.

Thoughts @mfranzke @annsch @nmerget ?

[mfranzke]

@dkolba this is related to the contents of CHANGELOG.md, isn't it? So it would mean to leave that file "empty"/untouched on release process and e.g. link to https://github.com/db-ui/elements/releases ?

[dkolba]

Yeah, CHANGELOG.md should be phased out then I guess.

[mfranzke]

Do we need a custom changelog at all?

We need to curate the releases entries content most likely.
Both we would need to ensure that our changes / pull requests only include code related to the aspects that are mentioned and well documented both in the commit message as well as further in the related issues, that are linked in the GitHub generated release listings as well.
Plus these listings include all of the commits in the delta of two tags – from now on we might want to focus on aspects that are relevant for the users of our packages, so we most likely would strip things out like (at least patch) dependabot dependency updates and further "internal" stuff, that isn't relevant for the packages that we provide to npm.

That for a CHANGELOG.md might be still a valid documentation with which we could additionally collect the necessary entries for a release with each PR, and than copy over its contents to the GitHub releases section on release.