fix: use brew upgrade --cask codex to avoid warnings and ambiguity
#9823
+1
−1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use `brew upgrade --cask codex` instead of relying on implicit cask resolution. Without `--cask`, Homebrew can emit a warning indicating that `codex` resolves to the `homebrew/cask/codex` cask. Being explicit avoids unnecessary noise and keeps the update command deterministic if a `codex` formula is ever introduced.
Contributor
|
All contributors have signed the CLA ✍️ ✅ |
Author
|
I have read the CLA Document and I hereby sign the CLA |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #9822
Summary
Make the Homebrew upgrade command explicit by using
brew upgrade --cask codex.Motivation
During the Codex self-update, Homebrew can emit an avoidable warning because the
name
codexresolves to a cask:While the upgrade succeeds, this relies on implicit name resolution and produces
unnecessary output during the update flow.
Why
--caskcodexformula is ever introducedContext
This restores the
--caskflag that was removed in #6238 after being considered“not necessary” during review: #6238 (comment).