👋 Hello @Burhan-Q, thank you for submitting your PR to the ultralytics/ultralytics 🚀 repository! This is an automated response, but rest assured, an Ultralytics engineer will assist you soon. In the meantime, please review the following checklist to ensure everything is in order for your contribution:

• ✅ Clarify Purpose: Make sure to clearly define the purpose and impact of your changes in the PR description. If applicable, link to any relevant issues to provide context.
• ✅ Stay Updated: Confirm that your branch is in sync with the ultralytics/ultralytics main branch. If there are any conflicts, resolve them by updating your branch with the latest changes.
• ✅ Pass CI Checks: Ensure all Continuous Integration (CI) checks pass successfully. If there are any issues, please address them promptly.
• ✅ Documentation: Update the documentation as needed to reflect your changes, especially if there are new or modified features.
• ✅ Testing: If relevant, add or update tests for your modifications and verify that all tests are passing.
• ✅ Contributor License Agreement: Please sign the Contributor License Agreement (CLA) if this is your first contribution to Ultralytics by stating "I have read the CLA Document and I sign the CLA" in a new comment on this PR.
• ✅ Keep It Concise: Limit the changes in your PR to the minimum necessary to accomplish your objective. "Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away." — Antoine de Saint-Exupéry

For additional guidance, refer to our Contributing Guide. Feel free to ask questions or seek clarification by leaving a comment. We appreciate your effort to enhance the CI workflow, making it more efficient with cache pruning! 🚀💾

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.01%. Comparing base (bf63170) to head (f77547a).
Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main   #17664      +/-   ##
==========================================
+ Coverage   73.97%   74.01%   +0.03%     
==========================================
  Files         128      128              
  Lines       17138    17138              
==========================================
+ Hits        12678    12684       +6     
+ Misses       4460     4454       -6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Burhan-Q can we combine these into the uv pip install step?

@glenn-jocher I can try moving this but was following the guidance of the uv docs to place after all tests have run. I'm guessing that since it removes all pre built packages, moving it forward might cause problems, but it's worth testing out.

@Burhan-Q yes I just read them and they recommend this as a final step.

I read some more on their README though and it seems like there is an argument there for cache pruning that is already set to default true, so I'm a little confused if since we are using the action and not just the CLI commands if this already covers us?

https://github.com/astral-sh/setup-uv/blob/1e4d4ea9ff6b65a6b126d250fc05cf16a2adf619/action.yml#L35-L37

Oh I see. That's curious bc adding the cache prune --ci step does remove items, but maybe that was in the "clean up" step by default and I just moved this forward... You're right the GHA has it enabled by default

I wonder if the cache prune command only runs by default if the cache is enabled for the action? I poked around the issues on the setup-uv repo and saw someone posted their logs, which show "Pruning cache" in the post setup-uv job clean up step, which isn't shown for the Ultralytics GHA runs. This user's workflow file does enable caching, so I'm wondering if that's why it doesn't run for ours and enabling the CLI command, that this PR introduces, ensures this runs.

@Burhan-Q merged!