astral-sh/uv

`uv self update` may leave uv unusable if interrupted

Open

#12,142 opened on Mar 12, 2025

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Rust (84,934 stars) (3,111 forks)batch import
bughelp wantedwindows

Description

Description:

The current update process renames uv.exe to uv.exe.previous.exe before completing. If interrupted (e.g., by network failures or manual termination), this can leave uv unusable due to an incomplete update.

Suggested Improvement:

Ensure atomic replacement where uv.exe is only modified after the new version is fully validated.

Contributor guide

Tech stack
rust
Domain
clitooling
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-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingfile system operations
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75
Research direction
Examine the self update command implementation in the uv repository, focusing on the file renaming and replacement logic. Identify the point where the old binary is renamed to a .previous extension before the new binary is fully downloaded and verified. Consider implementing atomic replacement by first writing the new binary to a temporary location, validating it (e.g., checksum or execution test), then atomically replacing the original file. Review existing test files related to self update to ensure coverage of interrupted scenarios.