Skip to content

feat: Windows MSI in CI and GitHub Releases - #7

Merged
ildella merged 1 commit into
masterfrom
feat/windows-msi
Sep 10, 2026
Merged

feat: Windows MSI in CI and GitHub Releases#7
ildella merged 1 commit into
masterfrom
feat/windows-msi

Conversation

@ildella

@ildella ildella commented Sep 10, 2026

Copy link
Copy Markdown
Owner

Why

Linux already builds unsigned AppImage/deb/rpm on PRs and ships signed artifacts on v* tags. Windows CI only compiled --no-bundle. This adds the same split for MSI so we can evaluate packaging before treating Windows as a product.

What

  • scripts/prepare-sidecar-bundle.js — host-aware sidecar staging (keep this-OS onnxruntime only). beforeBundleCommand runs it via Node so Windows CI does not need sh.
  • ci-windows.yml — unsigned tauri build -b msi on PRs/master.
  • release-windows.yml — on v*, tauri-action -b msi with updater artifacts, same tag/secrets as Linux so the MSI lands on the existing release and merges into latest.json.
  • npm run build:msi for a Windows host. Default bundle.targets stays deb.

Evaluate

  • PR CI produces an .msi (workflow ci-windows).
  • Sidecar prune keeps win32 on the Windows runner (and still strips foreign ORT on Linux).
  • Do not merge until we are okay shipping an experimental MSI: still needs Node on PATH + mpv; playback/clipboard are Linux-oriented; no Authenticode (SmartScreen).

Stage sidecar with a host-aware Node script so onnxruntime keeps win32
binaries. PR CI bundles MSI; tag workflow uploads a signed MSI onto the
same GitHub Release as Linux.
@ildella
ildella merged commit bd60143 into master Sep 10, 2026
3 checks passed
@ildella
ildella deleted the feat/windows-msi branch September 10, 2026 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant