Skip to content

v0.5.1: Fix broken launch in v0.5.0

Choose a tag to compare

View all tags
@darrylmorley darrylmorley released this 01 May 13:49
· 665 commits to main since this release
v0.5.1
a5c9b65

What's fixed

  • v0.5.0 broke app launch. The CLI binary was placed in the same directory as the menu bar binary (Contents/MacOS/). On the case-insensitive filesystem most Macs use, whatcable and WhatCable are the same path, so the second copy silently overwrote the first. The bundle shipped with the CLI binary masquerading as the main app, so launching WhatCable.app produced a one-shot CLI run instead of the menu bar UI. Anyone who installed v0.5.0 via the in-app updater or via Homebrew should upgrade to v0.5.1.

The CLI now lives at WhatCable.app/Contents/Helpers/whatcable, which is also Apple's expected location for bundled non-launch executables.

Install

Download WhatCable.zip, unzip, and drag WhatCable.app into /Applications. Notarised and stapled, no Gatekeeper warning.

If you installed via Homebrew, brew upgrade --cask whatcable will pull v0.5.1 and re-link whatcable on your PATH at the new location automatically.

If the in-app updater on a broken v0.5.0 install can't recover, run:

brew uninstall --cask whatcable
brew install --cask whatcable

or download WhatCable.zip from this release page and replace the bundle by hand.

Sorry

This was a last-minute bug in the v0.5.0 build script that none of the local tests caught because they ran against the freshly-built dist/ directory before the second copy clobbered the first. The build script now uses a separate directory for the CLI so the collision can't happen, and the test plan for future releases includes launching the installed .app end-to-end before publishing.

Assets 3
Loading