You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Found the cause of this bug. When version_source=tag, no new commits are created containing the version number. So, during generation of the changelog, we skip straight over where the version begins:
Any movement on this? I'm switching our CI to us semantic-release version with the tags option to avoid pushing commits from the pipeline. Currently, this defect means I'll just lose changelog generation. Not the end of the world, but not ideal either.
Activity
danth commentedon Feb 21, 2020
Found the cause of this bug. When
version_source=tag, no new commits are created containing the version number. So, during generation of the changelog, we skip straight over where the version begins:https://github.com/relekang/python-semantic-release/blob/e427658e33abf518191498c3142a0f18d3150e07/semantic_release/history/logs.py#L108-L111
Therefore the generated changelog is blank and GitHub replaces it with the tag message automatically.
[-]Release notes not posting properly[/-][+]Changelog generation broken in tag mode[/+]rpocase commentedon Apr 21, 2021
Any movement on this? I'm switching our CI to us
semantic-release versionwith the tags option to avoid pushing commits from the pipeline. Currently, this defect means I'll just lose changelog generation. Not the end of the world, but not ideal either.github-actions commentedon May 13, 2021
This bug report has been labelled as help wanted since there has been no activity in the last 3 weeks. It will not be closed.
fix: Fix changelog generation in tag-mode (python-semantic-release#171)
fix: fix changelog generation in tag-mode (python-semantic-release#171)
fix: fix changelog generation in tag-mode (python-semantic-release#171)
fix: fix changelog generation in tag-mode (#171)