Assume the --greedy
flag for brew outdated
when HOMEBREW_UPGRADE_GREEDY
is set
#17668
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
brew style
with your changes locally?brew typecheck
with your changes locally?brew tests
with your changes locally?If a user has set the
HOMEBREW_UPGRADE_GREEDY
env var, it implies that they are interested in always having their Casks upgraded "greedily" duringbrew upgrade
.It follows that such a user would additionally always be interested in knowing whether their Casks are "greedily" outdated when running
brew outdated
. Thus, this change makesbrew outdated
respectHOMEBREW_UPGRADE_GREEDY
in the same manner asbrew upgrade
.