ci: handle already-published release and crates.io version gracefully

Author: Michael-A-Kuykendall

.github/workflows/release.yml

@@ -317,10 +317,15 @@ jobs:
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: |
-          gh release create ${{ github.ref_name }} \
-            release-files/* \
-            --title "Shimmy ${{ github.ref_name }}" \
-            --generate-notes
+          if gh release view ${{ github.ref_name }} > /dev/null 2>&1; then
+            echo "Release already exists — uploading binaries to existing release"
+            gh release upload ${{ github.ref_name }} release-files/* --clobber
+          else
+            gh release create ${{ github.ref_name }} \
+              release-files/* \
+              --title "Shimmy ${{ github.ref_name }}" \
+              --generate-notes
+          fi
 
       - name: Install Rust for Rust steps
         uses: dtolnay/rust-toolchain@stable
@@ -331,7 +336,11 @@ jobs:
           CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
         run: |
           # Publish the crates.io-safe version (huggingface default, no airframe path dep)
-          cargo publish --no-default-features --features huggingface
+          if cargo publish --no-default-features --features huggingface 2>&1 | grep -q 'already exists'; then
+            echo "ℹ️  shimmy already published to crates.io — skipping"
+          else
+            cargo publish --no-default-features --features huggingface
+          fi
           echo "✅ Published shimmy to crates.io"
           echo "ℹ️  crates.io version uses huggingface engine. Airframe GPU binaries are in GitHub Releases above."
           echo "ℹ️  To use Airframe GPU: download the platform binary from GitHub Releases."