Skip to content

feat: notify users when a downloaded update is ready to install - #31

Merged
lonewolfyx merged 1 commit into
mainfrom
feat/app-update-notification
Jul 15, 2026
Merged

lonewolfyx merged 1 commit into
mainfrom
feat/app-update-notification

Conversation

@lonewolfyx

Copy link
Copy Markdown
Member

Add AppUpdateNotificationService that posts a macOS user notification once Sparkle has downloaded an update scheduled to install on quit. Tapping the notification activates the app and opens the Sparkle update window.

  • AppDelegate conforms to SPUUpdaterDelegate and triggers the notification from updater(_:willInstallUpdateOnQuit:immediateInstallationBlock:).
  • On launch, clear any delivered/pending notification whose build version matches the running build, so stale notices don't linger after install.
  • Track the last notified build version in UserDefaults and guard concurrent attempts with a lock to avoid duplicate notifications.
  • Add localized title and message strings for zh-Hans and en.

Co-Authored-By: Claude noreply@anthropic.com

Add AppUpdateNotificationService that posts a macOS user notification once Sparkle has downloaded an update scheduled to install on quit. Tapping the notification activates the app and opens the Sparkle update window.

- AppDelegate conforms to SPUUpdaterDelegate and triggers the notification from updater(_:willInstallUpdateOnQuit:immediateInstallationBlock:).
- On launch, clear any delivered/pending notification whose build version matches the running build, so stale notices don't linger after install.
- Track the last notified build version in UserDefaults and guard concurrent attempts with a lock to avoid duplicate notifications.
- Add localized title and message strings for zh-Hans and en.

Co-Authored-By: Claude <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 15, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@lonewolfyx, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 13 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: f6e4d80e-5d88-4535-a4a0-cde1e97376ad

📥 Commits

Reviewing files that changed from the base of the PR and between 107738d and 6869697.

📒 Files selected for processing (3)
  • Sources/AgentBar/App/AppDelegate.swift
  • Sources/AgentBar/Localization/I18n.swift
  • Sources/AgentBar/Services/AppUpdateNotificationService.swift
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/app-update-notification

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@lonewolfyx
lonewolfyx merged commit c5ee3b3 into main Jul 15, 2026
1 check passed
@lonewolfyx
lonewolfyx deleted the feat/app-update-notification branch July 15, 2026 06:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant