Fix upgrade flow outside git checkout#24
Merged
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.
What changed
conviso upgradefor installations running outside a git checkout0.3.8to0.3.9Why
The CLI was trying to run
git pullfrom the installed package path. For pip or wheel installs this is not a git repository, so users saw a misleading upgrade flow and could keep running an older binary.Impact
Users installing the CLI outside a local repository now get the correct upgrade instructions, including reinstall guidance and shell command refresh hints.
Validation
python3 -m py_compile src/conviso/app.pynew-commanndspushed with commit91b4e56