chore: categorize dependency updates and other changes in auto-generated release notes #1515
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.
Release note of grafana-operator seems to be generated by GitHub's auto-generation feature.
https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes
It is hard for us to read large number of changes that may contains important changes.
Special attention should be paid when important changes are mixed in with the large number of dependency change logs.
Fortunately, the PRs automatically generated by dependabot are labeled
dependencies
. This could be used to categorize the list of changes in the release notes to reduce the burden on the user.https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes#configuration-options
The release notes should now appear as follows:
The category titles are tentative, so if you have a good one, please let me know.