Ran into these. I dunno, I run into things, okay? Anyway. These are my beefs with Github Actions and Github pipelines in general. My therapeutic venting might save someone somewhere some grief. First off:
The Github Actions webhooks or whatever that listen for workflow trigger events: yeah, they don't care about the 'draft' status of your release. To me this is madness, because a draft is precisely what I'd want to listen for, to kick off a deployment workflow which, let's face it, may or may not faceplant. So that if a faceplant ensues, we can wave the whole thing away with a "bah, it was just a draft anyway, see?". But no. GA will shout it from the hilltops that you have FAILED, and that it can't and WON'T help you roll anything back. Like, it... WANTS you to release crap unto the world at large, PUBLICLY, that you can't take back.
Further underscoring GA's penchant for seeing folks twist in the wind:
Simple. But say it wasn't successful. Say you want to get back to how things were, and forget unfortunate recent events. Ha! Chance would be a fine thing. To back out of the release entirely, github has made this difficult to do for non-enterprise users, so plebeian freeloaders have to do this instead:
git push --delete origin <tagname>. This reverts the release to a plain 'draft' state.
.ymland even the workflow name itself (like, what??!). If it suddenly stops paying attention to your workflow updates, you might have to:
Here's the worst part: after effectively being forced to introduce a new workflow, the old one does not die. It can't die, unless you manually go to each run and nuke the logs. That's not gonna be practical for a workflow that's been around for a while. So, all you can really do is manually disable the old workflow. Ughetty-ugh to the power UGH.