@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 specifically came of it. I agree it would be a useful feature to provide methods of adoption of this project to an existing project.

Hi @codejedi365, sorry for the late response, thank you so much for replying, I think the ticket you mentioned was #722. Hope to see this feature in the future!

@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 template directory to write a custom template which does not loop through all of the versions as the provided default does. Jinja2 also provides the ability to import other files and macros. Potentially, you could correct your changelog for the previous versions and store that as a file such as 3.x_CHANGELOG.md. Then in your custom changelog template abort the loop when the version matches 3.x and just import the other file and append it. Unfortunately, Jinja does not support "break" so you likely will need to write a macro to filter out all versions below your threshold (ex. 4.x). This is a bit exploratory as I have not done this myself but thinking about it now I believe it accomplishes what you need.

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?

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 of devised a way to make this a reality. Hopefully over the next few months I can implement a solution.

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 option, changelog.mode) soon in v9. If you have a custom template configuration, you will need to modify your templates for the newly provided context variables for use.

My plan is to convert the placeholder functionality back to the default in v10. Stay tuned.

🎉 This issue has been resolved in version 9.10.0 🎉

The release is available on:

• PyPi package
• GitHub release

Check out the Changelog Templates in the documentation to learn about the "update" mode.