Obsidian - Require reinstall of Cask for version v1.8.4

[belthesar]

Verification

• I understand that if I ignore these instructions, my issue may be closed without review.
• I have retried my command with --force.
• I ran brew update-reset && brew update and retried my command.
• I ran brew doctor, fixed as many issues as possible and retried my command.
• I have checked the instructions for reporting bugs.
• I made doubly sure this is not a checksum does not match / SHA256 mismatch error (do not open an issue before trying to open a PR to fix first).

Description of issue

Hi folks - opening this issue because I wasn't sure if this made sense as a discussion topic given the security alert sent by Obsidian.

Users of Obsidian that have used in-app upgrades from a previous version to Obsidian v1.8.4 (my full version prior to reinstall: v1.4.16) are receiving an in-application notification from Obsidian that they need to fully reinstall the application in order to receive important security updates to Obsidian. Performing a brew upgrade --cask does not perform this removal as the Cask contains the auto_updates stanza. Users can easily perform this update as required by performing a brew upgrade --cask obsidian --force to force re-downloading and installing Obsidian, however it is my opinion that due to the nature of the security update, the Cask should be modified to perform the update process for users for this version.

I'm not aware if there are mechanisms with Cask formulae to flag users as "normally this autoupdates, but if this latest version according to Homebrew is equal to or newer than the existing version, then perform a full upgrade". If so, I believe this is an appropriate time for this. Barring that, publishing an update to the cask temporarily setting the auto_updates stanza and/or adding a caveats stanza informing users on how to perform the forced upgrade procedure for this version should be provided.

Command that failed

n/a

Output of command with --verbose --debug

n/a

Output of brew doctor and brew config

n/a

Output of brew tap

n/a

[bevanjkay]

Calling brew upgrade obsidian without the --force flag will upgrade the cask regardless of the auto_updates true. When a cask argument is passed to brew upgrade the auto_updates stanza is ignored as the user has suggested intent to upgrade the specific package.

I don't think there's anything we can do on the Homebrew side in this instance.

[belthesar]

Ahh gotcha. It seems that it's only ignored when doing a vanilla brew upgrade (--cask) without specifying the formula/cask. I don't mind that some of this is "learn how Homebrew cask upgrades work," as I was able to work around this problem myself without much issue. I do wonder if there could be additional care to address this kind of situation in the future, but that'd be beyond the scope of this issue. I'll close this issue as a result. Thanks for your time and consideration!