[canary-publish] Enhance release notes with package details #26
Conversation
This file contains hidden or 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
…ate createReleaseForTags to use packageData
…clude packageName in release notes
|
I'll self merge for quick confirmation, I'm sorry. |
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.
Issue
Type of Work
Description of Work
This pull request introduces the following updates to improve the release notes generation process:
Enhanced
getFilteredCommitMessages: Modified to considerpackagePathin the filtered commit messages for better traceability.Improved
createReleaseForTags: Updated to usepackageDatafor generating release notes.Included
packageNamein the release notes to provide more context about the changes.Review Points
Others