astral-sh/uv

uv tool upgrade - problem with private indexes due to short living credentials

Open

#8,523 opened on Oct 24, 2024

View on GitHub
 (10 comments) (4 reactions) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
bughelp wanteduv tool

Description

I am using uv tool install to install some CLI tools from private index (CodeArtifact).

When new version is released, uv tool upgrade generally fails. I have a mechanism that refreshes CodeArtifact index URL with new credentials and stores them in ~/.config/uv/uv.toml, but when tools are installed, index used is stored in uv-receipt.toml as far as I can tell and upgrade is trying to use that again. It usually fails, because those credentials are good only for couple hours.

Workaround is uv tool uninstall <tool> && uv tool install <tool>.

Should upgrade use globally defined index if stored one fails? Maybe only if domain is the same (but ignore credentials)? Not sure what the best approach is here, but it would be good for upgrade to work.

Happy to provide any additional details if needed.

❯ uv --version
uv 0.4.26 (1b9b9d56b 2024-10-23)

Contributor guide

Tech stack
rustpython
Domain
backendtoolingdeveloper experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Familiarity with uv toolBasic understanding of package index authentication
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
Investigate how uv stores index URLs in uv receipt.toml during tool install and how it uses them during tool upgrade. Consider modifying the upgrade logic to fall back to globally configured indexes (e.g., from uv.toml) if the stored index fails due to expired credentials. Look at the index resolution code and credential handling to ensure domain based matching. Check existing tests for tool upgrade and index handling.