fix(release): single multi-arch build, fixes failed v0.2.1 publish#67
Merged
Conversation
added 2 commits
June 24, 2026 18:24
The dist script now runs electron-builder once per arch and already passes --publish never to each. The release workflow also appended '-- --publish never', which npm adds to the last invocation, giving it --publish twice. Duplicated flags parse as an array that electron-builder no longer treats as 'never', so it auto-published on the tag and failed with no GH_TOKEN. Use plain 'npm run dist'.
…_LOG) Two chained electron-builder calls + the workflow's '-- --publish never' gave the last call --publish twice. A duplicated flag parses as an array, so electron-builder ignored 'never' and tried to auto-publish on the tag, failing with no GH_TOKEN. Use one 'electron-builder --win --x64 --arm64' call (like M2Station/M2_LOG), with --publish never applied once by the workflow. Produces combined + per-arch installers (x64, arm64).
oahsiao
changed the title
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.
The v0.2.1 release build failed with GitHub Personal Access Token is not set.
Cause: the 0.2.1
distchained two electron-builder calls (--x64then--arm64), each with--publish never. The release workflow also rannpm run dist -- --publish never; npm appends that to the last call, giving it--publishtwice. Duplicated flags parse as an array (["never","never"]), which electron-builder no longer treats asnever-> it auto-published on the tag and failed (no GH_TOKEN). The--x64call had it once, so only--arm64failed.Fix (mirrors the proven M2Station/M2_LOG setup):
distis now a single call:electron-builder --win --x64 --arm64.--publish neveris applied once by the workflow step.artifactNamemoved towinlevel:\ Setup \ \.\.Output (verified locally with the exact CI command): combined + per-arch installers, same as M2_LOG -
M2_GIT_DIFF Setup 0.2.1.exe(x64+arm64),... x64.exe,... arm64.exe.