FinalRun 0.1.10

What's changed in this release

Added — Windows x86_64 support

FinalRun now ships a finalrun-windows-x64.exe binary and a matching finalrun-runtime-0.1.10-windows-x64.tar.gz runtime bundle on every release.

End users on Windows install via PowerShell:

irm https://raw.githubusercontent.com/final-run/finalrun-agent/main/scripts/install.ps1 | iex

The Windows installer (scripts/install.ps1) mirrors the bash installer's structure: downloads the binary, extracts the runtime tarball, wires up the per-user PATH, and walks the user through Android tooling setup (Android Studio detection + scrcpy install via winget with a choco fallback). The iOS prompt is intentionally absent — iOS local execution requires xcodebuild (macOS-only). Cloud commands work the same on Windows for both Android and iOS.

finalrun upgrade now branches on platform: Windows hosts re-run install.ps1 via powershell.exe -Command "irm <url> | iex"; macOS/Linux hosts continue to re-run install.sh via bash -c "curl <url> | bash". Both honor the --ci flag.

Built via Bun's bun-windows-x64 cross-compile target on the existing Linux-based release runner; no new CI infrastructure or code signing pipeline yet (Windows users will see a SmartScreen warning on first run — click "More info → Run anyway"). A new smoke-windows job in the release workflow runs the cross-compiled .exe on a real windows-latest runner before tagging, blocking the release if the binary fails to execute.

Notes

• Windows ARM64 is not supported — Bun does not currently provide a bun-windows-arm64 cross-compile target.
• scripts/install.sh continues to reject Windows hosts (Cygwin / MinGW / MSYS / Git Bash). Windows installs go through install.ps1, not the bash installer.
• The Windows runtime tarball is byte-equivalent to the Linux x64 tarball (Android-only payload); the existing isDarwin gate in buildRuntimeTarball.mjs correctly excludes iOS bundles for non-darwin targets.