-
-
Notifications
You must be signed in to change notification settings - Fork 617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release 7.4.0 #2054
Release 7.4.0 #2054
Conversation
Failing test addressed here #2055 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks and welcome back @atugushev!
be0d600
to
0d7baa6
Compare
|
||
Features: | ||
|
||
- Allow force-enabling or force-disabling colorized output |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should really start styling the changelog writing with the past tense or present simple with references to comparisons with the previous release. Like using phrases along the lines of "X now does Y". The current content reminds a Git log rather than the release notes..
@atugushev The release notes for |
This is why I prefer tracking the change notes in Git 🤷♂️ |
Shall we add the |
@chrysle that's not enough. My extension only shows draft fragments but Towncrier itself is not integrated here so it'd need to become a part of the release process replacing the drafter first. It's a larger change in a lot of aspects. |
I'd be happy to take a look at that! Should we keep the changelog in RST, or rather use Markdown? |
Blocked by: