Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Addresses an issue with the changelog workflow by enhancing the way the release version is determined and set. Previously, the workflow relied solely on the input parameter for the release version, which did not accommodate cases where the changelog needed to be generated from a milestone title.
With this update, the workflow now checks if the event is a milestone and sets the
RELEASE_VERSIONenvironment variable accordingly. This ensures that the changelog can be accurately generated based on milestone titles when applicable, providing a more robust and flexible approach to versioning.By improving the changelog generation process, this change enhances the project's documentation quality and ensures that release notes are correctly associated with the appropriate versioning context. This ultimately leads to better clarity for contributors and users regarding project changes and updates.