My first fix was wrong about why the release could not be created. Gitea materialises a release row for every pushed tag, so the lookup should have found one; the create that followed hit a release that already existed. The lookup failed because of how it read the id. `sed 's/.*"id":\([0-9]*\).*/\1/'` is greedy, so `.*"id":` matches the last occurrence in the document, not the first — "id" appears again inside the nested author object — and it does not match `"id": 13` with a space after the colon at all. Checked against this instance: for v0.5.0, whose id is 12, the old pattern returns 1. It now greps the first "id", tolerates the whitespace, and re-reads the release after creating rather than parsing the create response, so a 409 resolves to the release that was already there instead of to an error. `set -e` was hiding the empty case: a command substitution in an assignment fails the script, and grep exits non-zero when it matches nothing, so the "no release yet" branch could never be reached — the job would simply stop. Both extractions are guarded, and both paths are exercised. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>