chore(ci): add release note generation #1040
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Allows for better changelogs for apps such as dependabot and renovate.
|
Ref #968 |
|
|
|
This PR is being marked as stale due to a long period of inactivity |
|
For now, we will continue with doing release notes by hand. We've removed the changelog #1634 since we hardly used it. Thank you so much for the contribution! |
|
Makes sense. Thanks for the update! :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows for better changelogs for apps such as dependabot and renovate.
Please compare the release notes sections here: aevea/release-notary#180 and here: aevea/release-notary#120
This PR will change to look like the latter. Non-conventional commit messages will go into
othersection meaning this does not break any flow. The advantage however is that people using Renovate will see the changes directly in theRelease Notessection and don't have to manually check.References #259