If the app is distributed via GitLab releases, the appcast will be of the form. If the app is distributed via GitHub releases, the appcast will be of the form. I’m using Homebrew on macOS with M1 pro, in a non-admin standard user account. There are a few different ways the appcast can be determined:

You can confirm the package was removed by trying to run the command again, or by checking where Homebrew packages are installed to and you will find the package you removed is no longer there. By checking the submitted version against the contents of an appcast, we can better detect these invalid cases. Removing a package from Homebrew is quick, as there is no need to download anything, it just deletes the Homebrew package from the Mac.

The main homebrew/cask repository only accepts submissions for stable versions of software (and documented exceptions), but it still gets pull requests for unstable versions. A simple way to solve the problem of accumulating dependencies of deinstalled things is to periodically run brew leaves and compare it against a list of wanted leaves, and recursively remove everything else. Note: The livecheck stanza is usually preferred, as it allows casks to be updated automatically.

The value of the appcast stanza is a string, holding the URL for an appcast which provides information on future updates. Use it when it makes sense functionally and document your reason clearly in the cask, using one of the templates: for clarity for consistency to prevent conflicts due to developer suggestion.

Brew cask remove without uninstall