ci: only publish to PyPI when semantic-release creates new version (#50)

The release workflow was failing because it attempted to publish to PyPI
even when semantic-release detected that the version already exists and
skipped creating a release.

This commit fixes the workflow to:
1. Check if dist/ directory exists after semantic-release runs
2. Only trigger PyPI publish if dist/ was created (new release)
3. Prevent publishing failures when no new version is released

This resolves the 'No such file or directory: dist/' errors in recent
release workflow runs.

Author: dreamiurg

.github/workflows/release.yml

@@ -47,12 +47,23 @@ jobs:
         run: uv pip install --system "setuptools>=61.0"
 
       - name: Release with Python Semantic Release
+        id: semantic-release
         env:
           GH_TOKEN: ${{ steps.app-token.outputs.token }}
-        run: uv run semantic-release version
+        run: |
+          set +e
+          uv run semantic-release version
+          echo "exit_code=$?" >> $GITHUB_OUTPUT
+          set -e
+          # Check if dist/ directory was created (indicates new release)
+          if [ -d "dist" ]; then
+            echo "new_release=true" >> $GITHUB_OUTPUT
+          else
+            echo "new_release=false" >> $GITHUB_OUTPUT
+          fi
 
       - name: Publish to PyPI
-        if: steps.app-token.outcome == 'success'
+        if: steps.semantic-release.outputs.new_release == 'true'
         uses: pypa/gh-action-pypi-publish@release/v1
         with:
           print-hash: true