ci: Fix double triggering of release workflows (#17)

.github/workflows/docker-release.yaml

@@ -1,12 +1,11 @@
 name: Docker Release
 
+# Only trigger on GitHub release publication, not on tag push.
+# When a release is created, GitHub fires both 'release' and 'push' events.
+# Using only 'release' prevents duplicate workflow runs.
 on:
   release:
     types: [published]
-  push:
-    tags:
-      - "v[0-9]+.[0-9]+.[0-9]+"
-      - "v[0-9]+.[0-9]+.[0-9]+-*"
 
 # Cancel in-progress runs for the same tag
 concurrency:

.github/workflows/docker.yaml

@@ -1,5 +1,8 @@
 name: Docker Build
 
+# Build and test Docker images on pushes to main and pull requests.
+# Note: Version tags (v*) are NOT included here - they trigger docker-release.yaml
+# via the 'release: published' event instead, to avoid duplicate workflow runs.
 on:
   push:
     branches: [main, master]
@@ -9,8 +12,6 @@ on:
       - "src/**/*.py"
       - "pyproject.toml"
       - ".github/workflows/docker.yaml"
-    tags:
-      - "v*"
   pull_request:
     branches: [main, master]
     paths:

.github/workflows/pypi-release.yaml

@@ -1,12 +1,11 @@
 name: PyPI Release
 
+# Only trigger on GitHub release publication, not on tag push.
+# When a release is created, GitHub fires both 'release' and 'push' events.
+# Using only 'release' prevents duplicate workflow runs.
 on:
   release:
     types: [published]
-  push:
-    tags:
-      - "v[0-9]+.[0-9]+.[0-9]+"
-      - "v[0-9]+.[0-9]+.[0-9]+-*"
 
 # Cancel in-progress runs for the same tag
 concurrency: