You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ci: keep setup-uv pruning the cache after the v10 bump
setup-uv v9.0.0 flipped the prune-cache default from true to false, so moving
v7 -> v10.0.1 silently changed cache behaviour: jobs now save unpruned uv
caches. Verified against the action manifests:
v7 prune-cache default: "true"
v10.0.1 prune-cache default: "false"
That matters at all seven call sites, not just the one that opts in explicitly.
staging-tests sets enable-cache: true because its self-hosted runners are
ephemeral, and the remaining jobs run on ubuntu-latest where the default 'auto'
caches anyway, as the comment in staging-tests already notes. Unpruned caches
grow against the repository's cache quota and can evict other entries.
Setting prune-cache: true restores the previous behaviour rather than leaving
it to an upstream default that has now moved once. Raised in review on 1775.
0 commit comments