Fix CI publish-release: upload to existing release instead of --clobber (v3.2.5)

The publish-release job failed because gh release create --clobber is not
supported in the CI runner's gh version. Changed to a two-step approach:
check if the release already exists (from manual gh release create), and
if so, upload artifacts with gh release upload --clobber. Otherwise create
a new release. This handles both cases without the delete+create race.

Author: redpersongpt

.github/workflows/release.yml

@@ -134,9 +134,18 @@ jobs:
             echo "No release artifacts found."
             exit 1
           fi
-          # --clobber replaces an existing release atomically (no delete+create race)
-          gh release create "$tag" "${files[@]}" \
-            --repo "$GITHUB_REPOSITORY" \
-            --title "$tag" \
-            --latest \
-            --clobber
+          # Upload assets to existing release, or create new release if none exists.
+          # This avoids the --clobber flag (unsupported in older gh) and the
+          # delete+create race condition.
+          if gh release view "$tag" --repo "$GITHUB_REPOSITORY" &>/dev/null; then
+            echo "Release $tag already exists — uploading artifacts"
+            gh release upload "$tag" "${files[@]}" \
+              --repo "$GITHUB_REPOSITORY" \
+              --clobber
+          else
+            echo "Creating release $tag"
+            gh release create "$tag" "${files[@]}" \
+              --repo "$GITHUB_REPOSITORY" \
+              --title "$tag" \
+              --latest
+          fi

package.json

@@ -1,7 +1,7 @@
 {
   "name": "opcore-oneclick",
   "private": true,
-  "version": "3.2.4",
+  "version": "3.2.5",
   "description": "OpCore-OneClick deployment utility",
   "author": "OpCore-OneClick contributors",
   "main": "dist-electron/electron/main.js",