Repository navigation
feat(updates): automatic background updates - #11
Merged
Merged
Conversation
…l fork One Sparkle flow for both install channels: the cask declares auto_updates, so brew never fights the self-updated bundle. Checks are forced on every launch — the retired "Check Automatically" toggle could have persisted false, which would silently kill both auto-update and the passive banner. The new "Update Automatically" toggle (default on) controls silent download + install only. A staged update relaunches immediately only while the app is in the background and the output device is idle; otherwise the menu and banner flip to "Restart to Update" with install-on-quit as the backstop. An update relaunch skips the multi-output teardown so the next instance adopts the still-default aggregate and audio never reroutes. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
pantafive
force-pushed
the
arch-review-fixes
branch
from
June 7, 2026 09:17
8581f43 to
8fee2ae
Compare
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
Updates now install themselves. The brew channel fork is gone — Caskroom detection, terminal-command alerts, the copy button — both install channels run the one Sparkle flow. Background checks are forced on every launch (the retired "Check Automatically" toggle could have persisted
false, which would dead-end users with no UI to recover); the new "Update Automatically" toggle, default on, controls silent download + install only. With it off, the old flow remains: banner + Update button.A staged update relaunches the app on the spot only while it's in the background and the output device is idle. Watching a movie or sitting in the popover instead flips the menu and banner to "Restart to Update", with Sparkle's install-on-quit as backstop. The update relaunch skips the multi-output teardown, so the next instance adopts the still-default aggregate and audio never reroutes through the restart.
The README is cut from 836 to 378 words: feature prose to a scannable list, implementation genealogy dropped.
Required follow-up before the release that ships this: add
auto_updates trueto the cask inpantafive/homebrew-tap. Without it,brew upgradewith a lagging cask downgrades the self-updated app.Test plan
make build,make test,make lintgreen