Fix uv tool self-upgrade recovery - #16
Open
muqiao215 wants to merge 1 commit into
Open
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
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
uv toolself-upgrade command construction to use flags supported by older uv releasesValidation
pytest tests/infra/test_install.py tests/infra/test_updater.py tests/infra/test_version.py -qracknerd-436b0c0with/root/.local/bin/uv tool install --force controlmesh==0.34.10 --python python3.12racknerd-436b0c0runtime after restart:controlmesh --version=0.34.10, package metadata =0.34.10, import path = uv tool site-packagesIncident context
racknerd-436b0c0previously failed Telegram-driven self-upgrade while onuv 0.10.10uv tool install --force ...but not the old--force-reinstallpath used by the app