Repository navigation
Description
Goal
Add Check for updates to the macOS menu bar helper and Klicky Bar on Omarchy, using the centralized CLI introduced in #193.
These are independent changes. A contributor can take either platform and submit a focused PR; this issue stays open until both checkboxes are complete.
- macOS menu helper
- Omarchy Klicky Bar
Starting points
- macOS:
packaging/macos/KlickyMenu.swift, especially the existing CLI client and asynchronous menu actions;scripts/test-macos-menu.py. - Omarchy:
packaging/omarchy-bar/Controller.qmlandControlsPanel.qml. Edit these source files, not the generated companion repository. - Shared behavior:
src/update.rs,klicky update --help, and the centralized-update section indocs/INSTALLATION.md.
Expected behavior
- Add a clearly labelled menu action that invokes
klicky update --checkonly when clicked. Reuse the existing asynchronous process pattern and give the CLI enough time for its bounded 15-second network request. - Show the CLI's installed/latest version and installation-channel guidance, or a concise failure message. Treat its output as display text rather than parsing English labels into a second version-comparison implementation.
- Offer an explicit user-controlled handoff to
klicky updatein a visible terminal, where its confirmation and package-manager prompts remain available. Source/unknown installations must keep their manual-update guidance. - Keep playback, selected pack, volume and startup choices unchanged during checks. Prevent duplicate concurrent checks, preserve menu responsiveness and keep checks silent.
- Do not add background polling, a separate network client or direct installer/package-file replacement in either helper.
Validation
Check the current-release, newer-release, offline/failure, older-engine-without-update and repeated-click cases. An older engine should get clear upgrade guidance rather than a crash or a second installation. Verify that checking while paused stays paused and does not launch an installer. Use controlled CLI responses for automated checks, then describe a real menu check on the platform available to you. State which platform your PR covers.
Update the relevant helper documentation. Coordinate in the issue before starting so two contributors do not take the same platform.
Activity