Current workflow waits for release confirmation and then creates GitHub release along with S3 uploads and docker pushes.
It is much more convenient to have release draft created before confirmation, so developer can change description and add make other manual changes to release before it gets published.
Then, when release is confirmed in CI (environment deployment is approved), existing elease is published by CI automatically.
Current workflow waits for release confirmation and then creates GitHub release along with S3 uploads and docker pushes.
It is much more convenient to have release draft created before confirmation, so developer can change description and add make other manual changes to release before it gets published.
Then, when release is confirmed in CI (environment deployment is approved), existing elease is published by CI automatically.