Automate Releases based on Tagging #1410
Conversation
Signed-off-by: Simeon Widdis <[email protected]>
Signed-off-by: Simeon Widdis <[email protected]>
| # Organizing the tagged PRs into unified categories | ||
| categories: | ||
| - title: 'Breaking Changes' | ||
| labels: | ||
| - 'Breaking Changes' | ||
| - 'breaking' |
There was a problem hiding this comment.
We already have a breaking label but no breaking-changes one, is there a difference between them that warrants having both?
There was a problem hiding this comment.
Upto you, somehow only breaking word didn't make sense to me.
There was a problem hiding this comment.
It looks like a >breaking label is used in the OpenSearch repo. For consistency maybe we should go with this?
|
The current state of the draft release is looking like this: https://github.com/opensearch-project/observability/releases/tag/2.1.0.0 |
This may only be from next release onwards, unless we want to go back and manually tag all PRs going into 2.6 |
Signed-off-by: Simeon Widdis <[email protected]>
Signed-off-by: Simeon Widdis <[email protected]>
Swiddis
requested review from
vmmusings and
YANG-DB
and removed request for
vmmusings
|
@Swiddis should we add the |
Yeah, the SQL repo defines infrastructure as "Changes to infrastructure, testing, CI/CD, pipelines, etc." |
Signed-off-by: Simeon Widdis <[email protected]>
Signed-off-by: Simeon Widdis <[email protected]>
|
Closing to re-base onto 2.x |
Description
Generating a GitHub Release involves a few steps: selecting the commit, creating a version bump, and creating the release notes file. Per work mentioned in #1406, this has been automated to be performed based on tag selection. This PR:
draft-release-notes-config.ymlto better reflect labels currently in useinfrastructureandskip-changelog, that need to be added to the repoauto-release.ymlenforce-labels.ymlIssues Resolved
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.