| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(channels): make uv detection reachable and its guidance correct The uv channel added in the third round was unreachable: uv tools enter through wrapper.py, which unconditionally declared DISTRIBUTION_ENV=pypi, and the environment always wins over path markers — so uv tool install users got pipx/pip guidance, whose advice (run pip inside the uv-managed venv) is exactly what uv tells users not to do. Detect the uv layout in the wrapper itself (sys.prefix under /uv/tools/) and report "uv" there. The guidance command was also wrong: uv names tools by their install requirement, so the message now says "uv tool upgrade gitcode-cli" (--from alias installs need their custom name). The symlink-collision hints lacked a uv entry entirely: a uv tool link in ~/.local/bin (the bootstrap fallback directory) fell through to the generic "remove the symlink" advice, which would break the uv channel entry instead of cleanly uninstalling it — add the matching marker with the proper uninstall guidance. Fourth review batch 1, issue 604 items 4 and 6. Co-Authored-By: Claude Code <noreply@anthropic.com> | 1 个月前 | |
fix(channels): make uv detection reachable and its guidance correct The uv channel added in the third round was unreachable: uv tools enter through wrapper.py, which unconditionally declared DISTRIBUTION_ENV=pypi, and the environment always wins over path markers — so uv tool install users got pipx/pip guidance, whose advice (run pip inside the uv-managed venv) is exactly what uv tells users not to do. Detect the uv layout in the wrapper itself (sys.prefix under /uv/tools/) and report "uv" there. The guidance command was also wrong: uv names tools by their install requirement, so the message now says "uv tool upgrade gitcode-cli" (--from alias installs need their custom name). The symlink-collision hints lacked a uv entry entirely: a uv tool link in ~/.local/bin (the bootstrap fallback directory) fell through to the generic "remove the symlink" advice, which would break the uv channel entry instead of cleanly uninstalling it — add the matching marker with the proper uninstall guidance. Fourth review batch 1, issue 604 items 4 and 6. Co-Authored-By: Claude Code <noreply@anthropic.com> | 1 个月前 |