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
{{ message }}
Repository navigation
Add extra details to release from commit message #223
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?
Interesting idea, need to put more thought into how this can be added. I'm leaning towards a paragraph section in a commit message but unfortunately that is not standard to commit parsers. One such answer could be a cli option or interactive cli prompt but this would be problematic for all the different types of automation this project supports and recommends. I partially think that the deprecation message goes into the breaking changes section of the commit which will be extracted separately during parsing. It would take a custom changelog to document them in a separate section.
Either way, still in the backlog and open to community PRs.
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?
Activity
github-actions commentedon Jul 6, 2024
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 commentedon Jul 6, 2024
Interesting idea, need to put more thought into how this can be added. I'm leaning towards a paragraph section in a commit message but unfortunately that is not standard to commit parsers. One such answer could be a cli option or interactive cli prompt but this would be problematic for all the different types of automation this project supports and recommends. I partially think that the deprecation message goes into the breaking changes section of the commit which will be extracted separately during parsing. It would take a custom changelog to document them in a separate section.
Either way, still in the backlog and open to community PRs.
github-actions commentedon Sep 5, 2024
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?
38 remaining items
feat(changelog-md): add additional release info section to default ma…
feat(changelog-rst): add additional release info section to default R…
feat(parser-angular): add functionality to parse out `NOTICE:` prefix…
feat(parser-emoji): add functionality to parse out `NOTICE:` prefixed…
feat(changelog-md): add additional release info section to default ma…
feat(changelog-rst): add additional release info section to default R…
feat(parser-angular): add functionality to parse out `NOTICE:` prefix…
feat(parser-emoji): add functionality to parse out `NOTICE:` prefixed…
feat(changelog-md): add additional release info section to default ma…
feat(changelog-rst): add additional release info section to default R…
feat(changelog): add additional release info to changeling from commi…
codejedi365 commentedon Feb 6, 2025
🎉 This issue has been resolved in Version 9.18.0 🎉
You can find more information about this release on the GitHub Releases page.