ci(release): disable tauri-action updater repack, upload .sig ourselves

Root cause: tauri-action runs a second "Packaging" pass after tauri CLI
finishes, which rewrites src-tauri/target/<target>/release/bundle/macos/
Psysonic.app.tar.gz with different bytes. The .sig produced by tauri CLI
no longer matches the new hash, so tauri-action silently deletes it —
leaving the directory with only .app and .app.tar.gz (no .sig for our
manifest generator to consume).

Fix: pass `includeUpdaterJson: false` to tauri-action so it skips the
repack + updater JSON upload entirely, then copy both the .app.tar.gz
and .app.tar.gz.sig produced by tauri CLI into the workspace root with
the expected asset names and `gh release upload` them.

Also disables build-linux and the Windows matrix entry during testing
to cut iteration time roughly in half.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

.github/workflows/release.yml

@@ -83,8 +83,10 @@ jobs:
             args: '--target aarch64-apple-darwin'
           - platform: 'macos-latest'
             args: '--target x86_64-apple-darwin'
-          - platform: 'windows-latest'
-            args: '--bundles nsis'
+          # TEMPORARILY DISABLED during macOS updater testing — faster turnaround.
+          # Re-add before the next public release.
+          # - platform: 'windows-latest'
+          #   args: '--bundles nsis'
     runs-on: ${{ matrix.settings.platform }}
     steps:
       - uses: actions/checkout@v5
@@ -128,6 +130,35 @@ jobs:
         with:
           releaseId: ${{ needs.create-release.outputs.release_id }}
           args: ${{ matrix.settings.args }}
+          # Disable tauri-action's own .app.tar.gz re-packaging + updater JSON
+          # upload — its repack overwrites the .app.tar.gz produced by tauri
+          # CLI and invalidates the matching .sig (the tauri-created signature
+          # no longer matches the repacked tarball's hash, so tauri-action
+          # silently drops the .sig). We upload both files ourselves below,
+          # and the generate-manifest job assembles latest.json.
+          includeUpdaterJson: false
+      - name: upload updater bundle + signature (macOS only)
+        if: runner.os == 'macOS'
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          set -e
+          VERSION=${{ needs.create-release.outputs.package_version }}
+          TARGET_ARG='${{ matrix.settings.args }}'
+          if echo "$TARGET_ARG" | grep -q 'aarch64'; then
+            TARGET="aarch64-apple-darwin"
+            ARCH="aarch64"
+          else
+            TARGET="x86_64-apple-darwin"
+            ARCH="x64"
+          fi
+          BUNDLE_DIR="src-tauri/target/${TARGET}/release/bundle/macos"
+          cp "${BUNDLE_DIR}/Psysonic.app.tar.gz"     "Psysonic_${ARCH}.app.tar.gz"
+          cp "${BUNDLE_DIR}/Psysonic.app.tar.gz.sig" "Psysonic_${ARCH}.app.tar.gz.sig"
+          gh release upload "app-v${VERSION}" \
+            "Psysonic_${ARCH}.app.tar.gz" \
+            "Psysonic_${ARCH}.app.tar.gz.sig" \
+            --clobber
 
   generate-manifest:
     needs: [create-release, build-macos-windows]
@@ -149,6 +180,9 @@ jobs:
           gh release upload "app-v${VERSION}" latest.json --clobber
 
   build-linux:
+    # TEMPORARILY DISABLED during macOS updater testing — faster turnaround.
+    # Re-enable by removing `if: false` before the next public release.
+    if: false
     needs: create-release
     permissions:
       contents: write
@@ -204,6 +238,11 @@ jobs:
   #
   # The refreshed lock/hash files are committed back to `main` when they change.
   verify-nix:
+    # TEMPORARILY DISABLED during the v1.34.x testing iteration (signing +
+    # updater stabilisation). Remove `if: false` to re-enable — it auto-commits
+    # flake.lock / npmDepsHash refreshes to main on every release, which causes
+    # rebase friction while we're iterating fast on the release pipeline.
+    if: false
     needs: create-release
     runs-on: ubuntu-24.04
     permissions:

CHANGELOG.md

@@ -9,6 +9,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 >
 > **🎉 macOS users:** Starting with **v1.34.15**, Psysonic can **update itself silently**. No more DMG downloading and dragging to Applications — the updater fetches the signed `.app` bundle, verifies the signature, replaces the app in place, and relaunches. Just click "Update" when the toast appears.
 
+## [1.34.16] - 2026-04-18
+
+### Fixed
+
+- **CI — Updater signature upload** *(by [@Psychotoxical](https://github.com/Psychotoxical))*: tauri-action on macOS produces the `.app.tar.gz.sig` minisign signature locally but does not upload it as a release asset for cross-target builds, which caused the `latest.json` manifest generator to fail (no signature to embed). An explicit post-build step now finds the `.sig` under `src-tauri/target/*/release/bundle/macos/` and uploads it with the expected filename (`Psysonic_aarch64.app.tar.gz.sig` / `Psysonic_x64.app.tar.gz.sig`).
+
 ## [1.34.15] - 2026-04-18
 
 ### Added

package.json

@@ -1,6 +1,6 @@
 {
   "name": "psysonic",
-  "version": "1.34.15",
+  "version": "1.34.18",
   "private": true,
   "scripts": {
     "dev": "vite",

src-tauri/Cargo.lock

@@ -3653,7 +3653,7 @@ dependencies = [
 
 [[package]]
 name = "psysonic"
-version = "1.34.15"
+version = "1.34.18"
 dependencies = [
  "biquad",
  "discord-rich-presence",

src-tauri/Cargo.toml

@@ -1,6 +1,6 @@
 [package]
 name = "psysonic"
-version = "1.34.15"
+version = "1.34.18"
 description = "Psysonic Desktop Music Player"
 authors = []
 license = ""

src-tauri/tauri.conf.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://schema.tauri.app/config/2",
   "productName": "Psysonic",
-  "version": "1.34.15",
+  "version": "1.34.18",
   "identifier": "dev.psysonic.player",
   "build": {
     "beforeDevCommand": "npm run dev",