Skip to content

v0.4.1

Choose a tag to compare

View all tags
@00mkp 00mkp released this 01 Oct 04:22
· 6 commits to main since this release
v0.4.1
2c68b89
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Banners now come from mutewake — its own name and icon — instead of Script Editor.

Changed

  • Wake/unlock banners post through the macOS notification center. On first run, macOS asks whether mutewake may send notifications; allow it. Banners never play a sound.
  • If you turn mutewake's notifications off, it respects that; the menu's Recent Activity notes "Banner off in Notifications settings" when one is skipped.
  • osascript remains only as a fallback for when macOS rejects the permission request outright.

Why it used to say Script Editor

The README blamed ad-hoc signing. The real cause was the build bug fixed in 0.4.0: the binary claimed a minimum macOS newer than the one it ran on, so LaunchServices never registered the app — which the notification center needs.

Notes

  • Your notification setting survives updates. The first run right after an install or mutewake update may briefly use the osascript fallback while macOS catches up with the rebuilt app; those banners still show as mutewake.
  • Corrected after release: an earlier version of these notes said each rebuild resets the permission. Testing showed it doesn't.

Updating

mutewake update                                    # from a clone
mutewake update ~/Downloads/mutewake-0.4.1.tar.gz  # from the archive below

New here? See the 0.4.0 release for install instructions.

Assets 2
Loading