Repository navigation
Keep pruning setup-uv caches - #157
Conversation
Change map
Requested change: keep today's pruning before merging Dependabot's setup-uv v10 bump (#25, #27). Today the 32 setup-uv cache entries (keys contain Smallest change: set the old default explicitly where caching happens. Steps with Verification:
Stopping condition: every caching |
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
72c472f to
990c10b
Compare
990c10b to
eb5b616
Compare
setup-uv v9 changed the prune-cache default to false, so the v10 bump (#25, #27) would start caching every downloaded wheel, including the 200-600 MB CUDA wheels. The repository's Actions cache is already at its ~10 GB limit with 5.7 GB of Rust caches, which unpruned uv entries would evict. Set prune-cache: true in the shared setup action and on every setup-uv step that caches (GitHub-hosted jobs using the default enable-cache: auto). It is already the default on v8.1.0, so nothing changes until the bump lands.
eb5b616 to
6b50452
Compare
What
Set
prune-cache: trueon everysetup-uvstep that caches: the shared setup action and 31 workflow steps.Why
setup-uv v9 changed the
prune-cachedefault tofalse. Once the v10 bump (#183) lands, uv cache entries would hold every downloaded wheel, including the 200–600 MB CUDA wheels, instead of only wheels built from source. The repository's Actions cache is already at ~10.4 GB, 5.7 GB of it Rust caches, which those entries would evict.prune-cache: trueis already the default on the pinned v8.1.0, so nothing changes until the bump merges, and the two can merge in either order.Change map and validation