codejedi365

@paduszyk Thanks for the report, I am working this effort it's just taken me some time to make it public in lieu of other priorities. There is a milestone for...

@paduszyk, one thing I forgot to mention is that if you wanted to see this resolved in your own projects today, you can easily define your own custom changelog template...

Still on the backlog, these changes were put on hold while I attended to other improvements and fixes

Likely not going to be changed until `v10` officially, for `v9` use it will require a custom template. Working on a fix for handling squash commits which is the primary...

### :tada: This issue has been resolved in version 9.13.0 :tada: The release is available on: - [PyPi package](https://pypi.org/project/python-semantic-release/9.13.0/) - [GitHub release](https://github.com/python-semantic-release/python-semantic-release/releases/tag/v9.13.0)

@Rebekah-Chuang, unfortunately there is not a current method for only prepending the latest release information. I do believe there was a previous ticket that mentioned this but it seems nothing...

@Rebekah-Chuang, given the complexities discussed in #722, I'm not sure if or when this feature would actually be solved, but there may be an alternative. You could use the changelog...

Still in the backlog however as I'm reviewing the changelog architecture and the performance of PSR, I am finding this issue to be one of more importance and I might...

I have found a solution that works for re-introducing the placeholder version update for changelogs using jinja. It will be released as a default changelog variation (toggled by a config...

### :tada: This issue has been resolved in version 9.10.0 :tada: The release is available on: - [PyPi package](https://pypi.org/project/python-semantic-release/9.10.0/) - [GitHub release](https://github.com/python-semantic-release/python-semantic-release/releases/tag/v9.10.0) ---- Check out the Changelog Templates in the...