ci: Update crates-release action to support manual trigger

This allows manually triggering the release of the internal crates.
Ideally the crates will be automatically released but a manual fallback
will be nice to have.

Assisted-by: Claude Code (Opus 4)
Signed-off-by: ckyrouac <ckyrouac@redhat.com>

Author: ckyrouac

.github/workflows/crates-release.yml

@@ -2,7 +2,8 @@
 name: Publish to crates.io
 on:
   push:
-    tags: ['v*']  # Triggers when pushing tags starting with 'v'
+    tags: ['v*']
+  workflow_dispatch: {}
 jobs:
   publish:
     runs-on: ubuntu-24.04
@@ -13,10 +14,19 @@ jobs:
     - uses: rust-lang/crates-io-auth-action@v1
       id: auth
     - run: |
-        for crate in bootc-internal-utils bootc-internal-blockdev; do
-          echo "Publishing $crate..."
-          cargo publish -p "$crate"
-          echo "Successfully published $crate"
+        # Publish crates if their current version is not already on crates.io.
+        # Order matters: dependencies must be published first.
+        CRATES="bootc-internal-utils bootc-internal-blockdev"
+
+        for crate in $CRATES; do
+          VERSION=$(cargo read-manifest -p "$crate" | jq -r '.version')
+          if cargo info "$crate@$VERSION" > /dev/null 2>&1; then
+            echo "$crate@$VERSION is already published, skipping"
+          else
+            echo "Publishing $crate@$VERSION..."
+            cargo publish -p "$crate"
+            echo "Successfully published $crate@$VERSION"
+          fi
         done
       env:
         CARGO_REGISTRY_TOKEN: ${{ steps.auth.outputs.token }}