* feat(updates): notify when a newer GitHub release is available
Check the configured release channel shortly after startup and every six
hours. When an update exists, show a tray menu item and a green New badge
on Settings → About, plus one desktop notification per version, so users
can open release notes and update themselves.
Co-authored-by: Jatin K Malik <jatinkrmalik@users.noreply.github.com>
* refactor(updates): slim UpdateMonitor after ponytail review
Drop unused APIs (tick/check_now/version injector/last_* state), integer-only
GLib scheduling, and the local demo launcher. Keep tray notify-send local to
avoid coupling to recognition_manager.
Co-authored-by: Jatin K Malik <jatinkrmalik@users.noreply.github.com>
* fix(updates): address Bugbot and harden notify persistence
Persist last_notified_version only after notify-send spawns successfully,
and sync the tray Update Available item from About-page checks without
re-notifying. Also merge latest main and cover the new paths in tests.
Co-authored-by: Jatin K Malik <jatinkrmalik@users.noreply.github.com>
* test(tray): pin config mock for update-notification assertions
CI on 3.9/3.10 showed empty MagicMock set call history after a successful
notify-send spawn. Pin tray.config_manager to the test mock and record set()
via side_effect so persistence checks are reliable across Python versions.
Co-authored-by: Jatin K Malik <jatinkrmalik@users.noreply.github.com>
* fix(updates): clear pending About update on failed lookup
A failed About check hid the New badge but left _pending_update set, so
clearing settings search could revive the badge while status still showed
the failed lookup. Clear dialog pending state on failure (tray unchanged)
and restore the badge via _set_about_update_badge.
* fix(updates): ignore stale UpdateMonitor results after channel switch
Bind the channel for each background check and discard the callback when
the configured channel changed mid-flight, then re-check immediately —
matching About-page stale-channel handling so the tray cannot show the
wrong channel's update state.
---------
Co-authored-by: Cursor Agent <cursoragent@cursor.com>
Co-authored-by: Jatin K Malik <jatinkrmalik@users.noreply.github.com>
