Closed charliedmcb closed 6 days ago
Totals | |
---|---|
Change from base Build 9621914521: | 0.0% |
Covered Lines: | 36287 |
Relevant Lines: | 37117 |
Totals | |
---|---|
Change from base Build 9621914521: | 0.0% |
Covered Lines: | 36287 |
Relevant Lines: | 37117 |
Totals | |
---|---|
Change from base Build 9621914521: | 0.0% |
Covered Lines: | 36287 |
Relevant Lines: | 37117 |
Totals | |
---|---|
Change from base Build 9621914521: | 0.0% |
Covered Lines: | 36287 |
Relevant Lines: | 37117 |
Fixes #
Description We currently have to create the github release, and its release notes manually.
The repo
aws
is using is no longer maintained:Because of this there are two approaches I'm looking at for our more automated release process.
I looked over the recommended substitutes and found that I think the action-gh-release might match our current desires the best. Its closest to the old action. However, the semantic-release action could also be useful with some of its additional feature sets, so want to explore that option as well, even though more complex. This PR is exploring the semantic-release option more.
I'm only giving the workflow the following perms, even though its known to now be enough:
How was this change tested? Sadly there isn't a great way to test this until we have it in main. *
Does this change impact docs?
Release Note