actions/setup-uv
1
0
Fork 0
mirror of https://github.com/astral-sh/setup-uv.git synced 2025-04-05 23:25:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Update README.md

Browse source
This commit is contained in:
Charlie Marsh 2024-10-24 19:07:10 -04:00 • committed by GitHub
parent 2a9ec8514a
commit 920219cac0
WARNING! Although there is a key with this ID in the database it does not verify this commit! This commit is SUSPICIOUS.
GPG key ID: B5690EEEBB952194
1 changed files with 3 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
README.md
View file

@ -170,7 +170,9 @@ It defaults to `setup-uv-cache` in the `TMP` dir, `D:\a\_temp\uv-tool-dir` on Wi
By default, the cache is pruned after a run, which means that all pre-built wheels are removed from
the cache ([documentation](https://docs.astral.sh/uv/concepts/cache/#caching-in-continuous-integration)).
If you want to keep the cache after a run, you can disable cache pruning with the `prune-cache` input.
By default, the uv cache is pruned after every run, removing pre-built wheels, but retaining any wheels that were built from source. On GitHub-hosted runners, it's typically faster to omit those pre-built wheels from the cache (and instead re-download them from the registry on each run). However, on self-hosted or local runners, preserving the cache may be more efficient. See the ([documentation](https://docs.astral.sh/uv/concepts/cache/#caching-in-continuous-integration)) for more.
If you want to persist the entire cache across runs, disable cache pruning with the `prune-cache` input.
```yaml
- name: Don't prune the cache before saving it