PHP Monitor 4.1 now requires at least macOS 11 (Big Sur). If you're using an older version of macOS, please install v4.0.
The recommended way of upgrading is running brew upgrade phpmon after you've installed PHP Monitor using Homebrew. It is recommended to run composer global update && valet install after upgrading, as this updates both Valet and your other dependencies.
It is also recommended that you run valet trust again before running the app if you're upgrading from v4.1.1 or older. For more information on why, read on.
What’s New In v4.1.2
This is a bugfix release for those folks having issues with v4.1 and v4.1.1, and mostly addresses #77.
Previously, Valet was invoked via the ~/.composer/bin path, but it is possible that running valet secure has created an entry in sudoers that references the symlink in the Homebrew bin directory instead. This will cause all superuser-enabled interactions with Valet (secure & unsecure, for example) to always fail. (Oops. That's no good!)
Since valet trust will always create the symlink, and since running valet trust is a requirement for the app to work correctly, PHP Monitor now uses the symlinked binary instead. Said binary should be able to run with superuser permissions without issues.
PHP Monitor might ask for you to run valet trust again at launch. If you're not sure your Valet installation is supported by PHP Monitor, you can run:
valet trust --off
valet trust
For changes in 4.1 and 4.1.1, please see the older release notes.