For example tag creation could be skipped when the sha would be the same instead of being a halting error.
Resuming a partial release is a more common release than trying to overwrite an existing release.

Ideas:

1. Make publish steps independent so one failure does not stop others
2. Persist publish state on disk as it progresses and then pick it up on subsequent runs
3. Make getsentry/publish parse the issue body which will have the targets listed as checkboxes
4. getsentry/publish action uses the the persistence file to sync the issue body to Craft