Replies: 1 comment
-
|
Thanks @shemeshg. You were not the main issue in that thread. Look at Homebrew/brew#21962 and Homebrew/brew#21946 for additional information and how you can opt-out. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Output of
brew configOutput of
brew doctorDescription of issue
Homebrew/brew#21965 (comment)
I never intended to sound impolite or rude. Communication styles vary significantly across cultures, and in some parts of the world people express themselves more directly or explicitly than what may be considered acceptable in the maintainers’ culture. ChatGPT also doesn’t always help bridge those differences effectively.
I understand that
auto_updatehas become more sophisticated and now correctly identifies the version from the info file, which is an improvement. However, having it upgrade automatically as part of a generalbrew upgradeis not the intended behaviour. I can see why explicitly runningbrew upgrade chromeshould work, but it shouldn’t be triggered implicitly during a fullbrew upgrade. I’m referring only to the default behaviour.Again, apologies for any unintended cross‑cultural misunderstanding.
Relevant casks
not applicable
Beta Was this translation helpful? Give feedback.
All reactions