fix(macos): retain update reminders and check on launch for 0.1.8 - #44
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.
The macOS menu app now checks quietly at launch and every six hours, and keeps Update Available… visible after closing an offer or choosing Later. A known eligible release survives presentation dismissal and transient errors; the reminder clears when Sparkle finds no eligible update, the user skips it, or installation completes. Launch revalidation avoids persisting stale feed data across app starts.
Prepares version 0.1.8. Downloads still require installation consent, and existing pause, exclusion, and recovery guards remain unchanged.
Validation: 83 UI and 156 core native tests passed, along with independent review, typecheck, privacy scan, and the 44-page docs build. The full Bun suite passed all 623 files in 8.1 minutes.
Security considerations: no signing, admission, credential, or recovery boundary changes. Apple Developer ID signing and notarization remain deferred; the existing authenticated feed/archive verification remains in force. Release publication and live installation are handled separately.
UI changes retain the existing menu appearance shown in #39; this change controls when its existing reminder appears and persists.