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.
This pull request enhances the release process by introducing automated and detailed release notes generation, along with minor adjustments to the release workflow and documentation updates. The key changes include creating a new workflow for release notes, modifying the existing build workflow to support detailed notes, and updating the
README.mdto document these features.Release Notes Automation:
.github/workflows/release-notes.yml: Added a new workflow to automatically generate detailed release notes on every new release. The notes categorize changes into features, bug fixes, maintenance, and others by analyzing commit messages.Workflow Enhancements:
.github/workflows/build.yml: Updated the build workflow to create aDETAILED_RELEASE_NOTES.mdfile and use it as the body for GitHub releases. The release name was also slightly modified for consistency.Documentation Updates:
README.md: Added a new section explaining the automatic release notes generation process, including how it works, commit message guidelines, and where to view the notes. A new feature about automatic release notes was also added to the feature list. [1] [2]