build(win): separate x64 + arm64 installers (v0.2.1)#66
Merged
Conversation
Build each arch in its own electron-builder invocation so NSIS emits two per-arch installers instead of a single combined ~176 MB file. - dist: electron-builder --win --x64 then --arm64 (both --publish never) - nsis.artifactName adds \: 'Setup 0.2.1 x64.exe' / 'Setup 0.2.1 arm64.exe' - bump 0.2.0 -> 0.2.1
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
1 participant
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.
What
Ship two separate per-CPU Windows installers for 0.2.1 instead of one combined file:
M2_GIT_DIFF Setup 0.2.1 x64.exe(~85 MB)M2_GIT_DIFF Setup 0.2.1 arm64.exe(~91 MB)Why
0.2.0 shipped a single combined x64+arm64 installer (~176 MB). ARM64 was included but not visible as its own download. This makes each architecture an explicit, smaller download.
How
distnow runs electron-builder once per arch (--win --x64then--win --arm64, both--publish never). A single multi-arch nsis target always also emits the combined installer, so per-arch invocations are the only reliable way to get exactly two files.nsis.artifactNameadds\so the files are clearly labelled.Verified locally
npm run distproduced exactly two installers (x64 + arm64), no combined.scripts/release.ps1(globSetup <version>*.exe) and CI (release/*.exe) both already pick up multiple installers, so no further changes needed.