fix: keep Homebrew in control of Ori updates - #2
Merged
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
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.
Summary
ORI_NO_UPDATE_CHECK=1for Homebrew launches so built-in update checks and automatic self-updates do not conflict withbrew upgradeWhy
The standalone installer writes an
ori.versionsidecar and Ori uses that marker to identify installer-managed binaries. A Homebrew installation should not carry that sidecar or allowori updateto replace files inside the Cellar.Verification
https://openrouter.ai/labs/ori/install.shscripts/checkbrew test OpenRouterTeam/tap/oriori updaterefuses to modify the Homebrew-managed binary