release: a re-run on a shipped tag gets past the release step (#133)

The first attempt at v0.1.174 cut the release and then stopped at the tap for
want of a token. Setting the token and re-running could never work: `gh
release create` fails when the release exists, and every step after it — the
tap bump among them — was skipped. So the one situation a re-run exists for
was the one it could not handle.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>

Author: dallasbpeters

.github/workflows/release.yml

@@ -141,10 +141,22 @@ jobs:
           echo "asset=/tmp/$NAME.tar.gz" >> "$GITHUB_OUTPUT"
           echo "name=$NAME.tar.gz" >> "$GITHUB_OUTPUT"
 
-      - name: Create the GitHub release
+      # Re-runnable on a tag that already shipped.
+      #
+      # `gh release create` fails outright when the release exists, and every
+      # step after it — the tap bump included — is skipped. That is exactly the
+      # shape of a re-run: the first attempt cut the release and then died at
+      # the tap for want of a token, and the retry could never get past here.
+      - name: Create or update the GitHub release
         env:
           GH_TOKEN: ${{ github.token }}
-        run: gh release create "${GITHUB_REF_NAME}" --generate-notes "${{ steps.build.outputs.asset }}"
+        run: |
+          if gh release view "${GITHUB_REF_NAME}" >/dev/null 2>&1; then
+            echo "Release ${GITHUB_REF_NAME} exists — replacing its asset."
+            gh release upload "${GITHUB_REF_NAME}" "${{ steps.build.outputs.asset }}" --clobber
+          else
+            gh release create "${GITHUB_REF_NAME}" --generate-notes "${{ steps.build.outputs.asset }}"
+          fi
 
       - name: Compute the tarball checksum
         id: sum