Repository navigation
Restore updater compatibility in Signboard 1.7.1 - #51
Merged
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.
Summary
com.electron.signboardapplication identity used by installed Signboard releasesWhy
Signboard 1.6.0 can discover 1.7.0, but its downloaded update cannot replace and relaunch the installed app because 1.7.0 was packaged with a different bundle/application ID. Keeping the existing identity restores the supported in-place update path.
Verification
npm run test:release-artifactsCFBundleIdentifier = com.electron.signboardand version1.7.1The separate 2.0 work is not included in this branch.