fix(release): set a safe packaged executable name#467
Merged
Conversation
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 recovered v0.6.1 workflow passed native ABI preparation, then Electron Builder 26.15 rejected the scoped package-derived Linux executable name
@spoolapp. Set the explicit packaged executable name toSpooland lock the configuration down with a regression test.\n\nVerification:\n-pnpm vp test run apps/app/scripts/lib/dev-launch-plan.test.mjs\n-pnpm vp check\n\nThe failed run produced no release or npm publication; this is the next same-version recovery checkpoint.