onWatch 2.14.1 is a follow-up to the 2.14.0 feedback round: three fixes, no new features.
Fixes
onwatch update works from a beta build (#123). The version compare dropped the pre-release suffix, so a machine on 2.14.0-beta.3 was told it was already at the latest version. Pre-releases now sort below the release they lead to, and identifiers compare the way semver says (beta.9 before beta.10, beta before rc).
The tray companion retires itself (#124). On Linux and Windows the tray icon outlived its daemon: a crash, a kill, or an onwatch stop that ran with a different HOME or LOCALAPPDATA than the start did left a gray dash behind with no way to remove it. The companion now watches the daemon that spawned it and quits about 30 seconds after that daemon is gone. A daemon that comes back inside that window is adopted, including under a new PID, and a dashboard still answering on the port counts as alive, so a restart never flickers the icon. Windows process liveness is stricter too: a handle to an exited process stays openable while anything holds one, so both callers now check whether the process object has been signalled.
Windows quick view placement is reportable (#125). Every quick view open now logs the cursor, the work area it came from and the window position it chose to menubar.log:
level=INFO msg="quick view anchor" cursor=1830,1417 work_area=0,0,2560,1400 work_area_source=monitor window=1552,712 size=360x680
If the window lands on the wrong display or edge with a side-docked taskbar, a taskbar on a secondary display, or mixed DPI, that one line is the whole bug report.
Upgrading
onwatch update, or re-run the installer.
If you are on a 2.14.0-beta.x build, onwatch update still reports you as current: the fix lives in the new binary, and the old one is the one doing the compare. Install 2.14.1 once from the assets below and updates work from there on.
The VS Code extension is unchanged in this release. It shares the daemon's version number, so 2.14.1 is a republish of the same extension.