Release PR Generation: Use prerelease tag in changelog generation #892
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
onetechnical
approved these changes
Aug 26, 2024
Contributor
onetechnical
left a comment
onetechnical
left a comment
There was a problem hiding this comment.
I guess there's some hokeyness when handling beta releases, since they aren't exactly new releases; I suppose new versions of beta will still include previous beta changes. Overall I think this is fine, but may involve manual work to clean up follow up beta releases.
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.
Use the prerelease tag when generating the changelog for release PRs.
If a prerelease version is specified, right now that is not used when generating the release PR with the planned version tag.
For example, that causes this statement to be at the end of the changelog:
Instead of:
I manually updated it in #891, but it would be nice to fix this at the source