Repository navigation
Windows: add an Arm64 installer to releases (1.0.8) - #18
Merged
Merged
Conversation
The Windows job now runs on windows-latest (x64) and windows-11-arm (Arm64), each freezing the app with its own native Python, and the release gets both LLM-Usage-Widget-<ver>-windows-x64-setup.exe and -windows-arm64-setup.exe. build.ps1 takes the architecture from the Python running PyInstaller and passes it to Inno Setup, which restricts the arm64 installer to Arm64 PCs (the x64 one still installs there under emulation). Both share the AppId, so either upgrades the other. Inno Setup is installed with Chocolatey on the Arm runner, which doesn't ship it. The tests also run on windows-11-arm with Python 3.11 to 3.14. Bump version to 1.0.8. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 of 2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
windows-latest(x64) andwindows-11-arm(Arm64). Each freezes the app with its own native Python, gets signed and verified the same way, and uploadsLLM-Usage-Widget-<ver>-windows-x64-setup.exe/-windows-arm64-setup.exeto the release.sysconfig.get_platform()) and passes/DAppArchto Inno Setup. installer.iss names the output by architecture and setsArchitecturesAllowed: the arm64 installer is limited to Arm64, and the x64 one also runs on Arm64 under emulation. Both share one AppId, so either one upgrades over the other.windows-11-armwith Python 3.11–3.14. setup-python has no Arm64 builds before 3.11.Heads-up: the x64 installer's filename changes from
-windows-setup.exeto-windows-x64-setup.exe. The in-app update check links to the release page, not to a specific asset, so it isn't affected.Test plan
installer.isslocally withAppArch=x64andAppArch=arm64. Both produce the expected filenames.Build installersworkflow (run it manually on this branch): both Windows matrix legs build, sign and verify. The arm64 leg is the new one: setup-python Arm64, PyInstaller/Pillow wheels, Chocolatey Inno Setup, and the Trusted Signing action on Arm.windows-11-arm.🤖 Generated with Claude Code