Homebrew Casks are used to put in pre-compiled purposes. Plenty of these include their very own replace mechanism, so having them replace each internally and through brew improve results in points. There’s a part within the Homebrew FAQ overlaying this.
From that part:
Something put in with Homebrew Cask ought to behave the identical as if it have been put in manually. However since we additionally wish to help software program that doesn’t self-upgrade, we add
auto_updates trueto casks for software program that does, which excludes them from brew improve.
The formulae for each Discord and Figma have auto_updates true set.
Because of this any replace can be triggered by the applying itself. These replace mechanisms aren’t conscious of the modified folder location although (this solely impacts Homebrew), so that they both get confused or set up the replace to the default place.
The simplest approach out of this in all probability is to put in these purposes to /Purposes (and never onto an exterior disk). If you’re low on disk area, you may also disable auto-update throughout the purposes (or cancel any replace try) and run brew replace discord figma recurrently (which can power a Homebrew-driven replace even for self-updating purposes).
PS: So far as I can see, at the very least Discord would not permit to stop auto-updates. Operating brew replace discord earlier than beginning it might the most suitable choice then.
