fix(ci): publish releaseType=release + force Node 24 for JS actions

═══ macOS artifacts missing from v1.4.6 release — root cause + fix ═══

Symptom — v1.4.6 release on GitHub had only Linux + Windows assets;
all macOS .dmg / .zip / blockmap / latest-mac.yml were missing.

Root cause — concurrent jobs racing to publish:
  • Windows job is fast (~3 min, no notarization). It uses
    softprops/action-gh-release@v2 which creates a PUBLISHED release.
  • macOS job is slow (~6 min, Apple notarization). It uses
    `electron-builder --publish always`. electron-builder's default
    publishing type is `draft`. When it tried to push to v1.4.6, it
    found an EXISTING release (created by softprops) of type
    `release`, refused to mix types, and silently skipped all
    uploads with: "GitHub release not created — reason=existing
    type not compatible with publishing type tag=v1.4.6 ...
    existingType=release publishingType=draft".

Fix:
  publish.releaseType = "release"

Now electron-builder publishes in `release` mode too, matching what
softprops creates, so it appends to the existing release instead of
skipping. Both publish paths now converge on the same release.

═══ Node 20 deprecation warning ═══

GitHub Actions emits a warning that JS-based actions running on
Node 20 will be forced to Node 24 by June 2nd, 2026 and Node 20
removed September 16th, 2026. softprops/action-gh-release@v2 still
ships Node 20 today.

Fix:
  env.FORCE_JAVASCRIPT_ACTIONS_TO_NODE24 = "true"  (workflow level)

This opts every JS action into Node 24 immediately, aligning with
our actions/setup-node@v5 + node-version 24 already used for the
build. Silences the warning and pre-empts the forced cutover.

Author: TigerTag-Project

.github/workflows/build.yml

@@ -8,6 +8,15 @@ on:
 permissions:
   contents: write
 
+# Opt every JS-based action in this workflow into Node.js 24. softprops/
+# action-gh-release@v2 still ships Node 20 binaries today and GitHub
+# Actions has scheduled the Node-20 deprecation for June 2026 / removal
+# in September 2026. Setting this flag now silences the deprecation
+# warning and aligns the action's runtime with our `actions/setup-node`
+# version (24).
+env:
+  FORCE_JAVASCRIPT_ACTIONS_TO_NODE24: "true"
+
 jobs:
   build:
     strategy:

package.json

@@ -34,7 +34,8 @@
     "publish": {
       "provider": "github",
       "owner": "TigerTag-Project",
-      "repo": "TigerTag_Studio_Manager"
+      "repo": "TigerTag_Studio_Manager",
+      "releaseType": "release"
     },
     "files": [
       "main.js",