e12820f150
Release / release (push) Failing after 21s
Previous implementation silently assumed any missing 'id' in POST response meant "release already exists", then called an unguarded python3 on the fallback response — which crashes (exit 1) if the fallback also fails (e.g. release really doesn't exist). New logic: - Build JSON payload in Python (avoids shell escaping + CLI length limits) - Capture HTTP status explicitly - 201 → success - 409 or "already exists" message → reuse existing (with HTTP check on fetch) - Anything else → fail loudly with the response body printed This also unblocks diagnosis of the current v0.1.0 failure by surfacing the actual error the Gitea API is returning.