b5178fd9ee
electron-builder emits Fusion-<v>-linux-x86_64.AppImage for x64 (deb uses amd64, tar.gz uses x64). The verify step globbed -linux-x64.AppImage and failed with "No Fusion Linux x64 AppImage artifacts produced" even though the AppImage built. Upload globs already used the broad -linux-*.AppImage. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1.4 KiB
1.4 KiB
@runfusion/fusion
| @runfusion/fusion |
|---|
| patch |
Fix the Binary Release workflow so platform binaries publish to GitHub Releases again:
- The release job now tolerates a single failing build leg instead of being skipped, which previously suppressed all assets.
- The node_modules cache key includes CPU arch so arm64 runners no longer restore x64 native deps (fixes the
@rollup/rollup-linux-arm64-gnubuild crash). - The macOS and Windows CLI signing steps are skipped gracefully when their certificate secrets are absent, so unsigned binaries still publish.
- Desktop packaging now invokes
electron-builderdirectly viapnpm execinstead of thedist:*scripts: pnpm leaked the--separator into script args, which made electron-builder ignore--publish never(auto-publishing to the wrong repo and 404ing) and drop the Linux--x64 --arm64flags. - The desktop build spawns workspace
.cmdbins with a shell on Windows, fixing thespawn EINVALfailure. - The desktop package declares an
authorwith email so the Linux.debtarget (fpm) can build. - The Linux AppImage verify step matches electron-builder's actual x64 output name (
-linux-x86_64.AppImage). - A workflow_dispatch run now builds and uploads binaries as artifacts for validation without creating a release (release creation is gated to tag pushes).
- The dependency-graph plugin build uses a cross-platform copy step that no longer breaks the Windows desktop build.