All pre-release changelog on release.

[cvalentin-dkt]

All pre-release changelog on release.

[ibiscp]

I was hoping to have the same behaviour here, if we generate pre-releases constantly, and after some time we generate a release, the release note is empty, it would make sense to have an option to consolidate all the pre-releases changes in the release.

I believe the rule shoul be:

• pre-release - Consolidate all changes since the last pre-release or release
• release - Consolidate all changes since the last release

[codejedi365]

An interesting concept, this might be a place for a jinja macro to preprocess the release history object that is passed to the environment of the template renderer and then loop through the resulting object.

I've personally never written a jinja macro but that would be where I would start.

[codejedi365]

After re-reading this, I'm not sure what is your intended outcome for the changelog?

1. Consolidate all prereleases commits to be under the full release version without the prerelease tags as sections?

Or

2. Consolidate all prereleases commits under the full release version while maintaining each prerelease section?

[cvalentin-dkt]

What would be interesting is that each "pre-release" has its own change log (as currently).
And when i create the "release", all the previous commits of the different RCs appear in the github changelog.
=> https://github.com/{org}/{repo}/releases/tag/vX.X.X

Actually, just last commit beetwen last RC and release is appear.

[codejedi365]

I think we are talking past each other given the terminology. I was specifically talking about the generation of CHANGELOG.md but it seems you were more interested in the GitHub Release Notes (a per version section of the changes).

My understanding is that right now, the release notes are properly generated for each pre-release but you would like to have the newest full tag release to include all of the commits between it and the last full release as if the prereleases never existed. Is this correct?

Actually, just last commit beetwen last RC and release is appear.

In other words: At the current moment, only commits between the last prerelease and the new release are posted in the new versions release notes. This is my understanding, yes.

I do not believe this is possible at the current time. I have recently made a fix (#822) which likely will provide this functionality for repos that follow the Git Flow merging strategy. I have not yet tested other strategies and I do not know their outcomes but might be related to making this possible.

[codejedi365]

@ibiscp, thank you for providing your input

[github-actions]

It has been 60 days since the last update on this confirmed issue. @python-semantic-release/team can you provide an update on the status of this issue?

[codejedi365]

Still in the backlog but a valuable improvement nonetheless