From 920219cac0f04e0f452c8c42418abe176d90d4d6 Mon Sep 17 00:00:00 2001 From: Charlie Marsh Date: Thu, 24 Oct 2024 19:07:10 -0400 Subject: [PATCH] Update README.md --- README.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 86386de..67df4eb 100644 --- a/README.md +++ b/README.md @@ -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