chore(ci): increase release automation and limit to one manual step#1297
Conversation
Signed-off-by: heitorlessa <[email protected]>
Signed-off-by: heitorlessa <[email protected]>
Signed-off-by: heitorlessa <[email protected]>
|
@rubenfonseca @leandrodamascena -- need your input the most here. Please let me know if this is clear, and whether there are any areas you want to me further document now (or later?). |
|
Hello @heitorlessa. Thanks for tagging me. This PR makes announcing new releases even more interesting as it automates all the work in the repository and allows for human interaction by writing text (and with images) announcing the release. I can't think of anything to add to the documentation right now. But I'll let you know if I think of anything new. Congrats 💯 🚀 |
|
@rubenfonseca need your approval before I fix a conflict and merge |
* develop: chore(deps): bump jsii from 1.61.0 to 1.62.0 (aws-powertools#1294) chore(ci): experiment with conditional on outputs chore(ci): improve error handling for non-issue numbers fix(ci): address conditional type on_merge chore(ci): add end to end testing mechanism (aws-powertools#1247) chore(deps-dev): bump mypy-boto3-appconfig from 1.24.0 to 1.24.29 (aws-powertools#1295)
…essa/aws-lambda-powertools-python into chore/changelog-automate * 'chore/changelog-automate' of https://github.com/heitorlessa/aws-lambda-powertools-python:
rubenfonseca
left a comment
There was a problem hiding this comment.
This is great work. Have you considered writing a book on Github Actions automation? 💯
Issue number: #1009
Summary
Changes
This PR reduces operational overhead when releasing a new version by restricting manual steps to a single job: Drafting release notes.
Main changes
User experience
Checklist
If your change doesn't seem to apply, please leave them unchecked.
Tasks
Separate PR to limit failure radius
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.
View rendered .chglog/CHANGELOG.tpl.md
View rendered MAINTAINERS.md