Latest Results
Release the cache lock while child processes run; make autoprune growth-triggered
Long-lived commands (uv run, uvx, uv format, uv check) previously held the
shared cache lock for the lifetime of the child process, blocking cache
maintenance for entire sessions. Instead, claim per-entry in-use locks on
the cache entries the child runs from, then release the main lock before
waiting on the child. Removal operations (autoprune, uv cache prune/clean,
uv cache clean --package) retain entries whose in-use lock is held; clean
without --force waits for in-use entries to be released.
With mid-session pruning now possible, replace the daily autoprune interval
with a growth trigger: prune when the archive bucket has grown by at least
32 entries since the last run, with a one-hour floor against churn.TrevorBurnham:cache-autoprune-exclusive-lock Latest Branches
0%
renovate/uuid-1.x-lockfile 0%
renovate/quote-1.x-lockfile 0%
renovate/codspeedhq-action-4.x © 2026 CodSpeed Technology