Add release.yml for automatic release note generation #2805
Conversation
This file contains 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
# Motivation To make our lives easier when doing releases we want to adopt the GitHub automatic release note generation feature. # Modification This PR adds the `release.yml` file to the repo and aligns the expected labels with the ones from OpenAPI. We have decided to use the OpenAPI labels going forward since those have been thought out quite well. After this PR is merged and before the next release I am going to rename the SemVer labels in this repo. # Result Easier releasing in the future.
glbrntt
approved these changes
Jul 24, 2024
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.
Motivation
To make our lives easier when doing releases we want to adopt the GitHub automatic release note generation feature.
Modification
This PR adds the
release.ymlfile to the repo and aligns the expected labels with the ones from OpenAPI. We have decided to use the OpenAPI labels going forward since those have been thought out quite well. After this PR is merged and before the next release I am going to rename the SemVer labels in this repo.Result
Easier releasing in the future.