On an Apple Silicon system with 2 Homebrew installations (at /opt/homebrew and /usr/local for arm64 and x86_64 respectively), arch --x86_64 /usr/local/bin/brew autoupdate subcommand conflicts with /opt/homebrew/bin/brew autoupdate subcommand, which makes it impossible to enable autoupdate for both installations simultaneously.
The workaround I've used here may not be suitable for wider adoption, but hopefully a few revisions will get it there if not.
TL;DR:
the LaunchAgent's name now includes the applicable architecture (e.g. com.github.domt4.homebrew-autoupdate.arm64)
the previous name is kept if ~/Library/LaunchAgents/com.github.domt4.homebrew-autoupdate.plist already exists (the new name only takes effect after brew autoupdate delete)
On an Apple Silicon system with 2 Homebrew installations (at
/opt/homebrewand/usr/localfor arm64 and x86_64 respectively),arch --x86_64 /usr/local/bin/brew autoupdate subcommandconflicts with/opt/homebrew/bin/brew autoupdate subcommand, which makes it impossible to enable autoupdate for both installations simultaneously.The workaround I've used here may not be suitable for wider adoption, but hopefully a few revisions will get it there if not.
TL;DR:
com.github.domt4.homebrew-autoupdate.arm64)~/Library/LaunchAgents/com.github.domt4.homebrew-autoupdate.plistalready exists (the new name only takes effect afterbrew autoupdate delete)~/Library/Logs/com.github.domt4.homebrew-autoupdate/isn't deleted unless it's emptyThere are probably things I've missed, but it seems to be working as expected here (although I don't have
--upgradeenabled).