Changelog entries get muddled when updating branch with merge commit

[DiamondJoseph]

Merging main into a branch to ensure the changes are up to date [and on merging the change in github?] leaves any new changelog entries in place next to whatever entries they were written next to, which means if the merge commit is resolved after a release has been made the change is incorrectly claimed to be included in a previous release. This requires extra care from developers and reviewers to ensure the changelog is accurate.

Can we automate production of the changelog, perhaps with release-please (which maintains a PR that updates every time a PR is merged, merging it can then trigger the release workflow, example)?