Use shared setup-uv action everywhere

[glenn-jocher]

Summary

• replace all 4 Astral uv setup steps with the shared retried owner
• preserve existing Python and environment behavior

Reused: ultralytics/actions/setup-uv@main is the single latest-uv installer owner.

Deleted: 4 direct astral-sh/setup-uv dependencies and obsolete Astral-only cache inputs where present.

Validation

• zero executable astral-sh/setup-uv occurrences
• all setup callers are exactly ultralytics/actions/setup-uv@main
• actionlint on changed workflows; any reported warnings are pre-existing on unchanged lines
• git diff --check
• shared owner passed Windows, Ubuntu, and macOS CI

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

🔧 Updated CI and publishing workflows to use Ultralytics’ shared setup-uv GitHub Action.

📊 Key Changes

• Replaced astral-sh/setup-uv@v7 with ultralytics/actions/setup-uv@main in:
  • Continuous integration workflows.
  • Package publishing and build jobs.
  • Software bill of materials (SBOM) generation.
• Removed the previous custom UV cache configuration from the CI workflow.

🎯 Purpose & Impact

• ✅ Standardizes UV setup across Ultralytics repositories.
• ⚙️ Centralizes dependency and tooling configuration in a reusable shared action.
• 🚀 Simplifies future maintenance and keeps CI, publishing, and SBOM workflows consistent.
• 📦 No direct changes to package functionality; the impact is limited to development and release automation.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/template 🚀 PR! This is an automated message; an engineer will assist with review. To ensure a seamless integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/template main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don't hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Clean PR. The shared setup action installs uv without enabling a cache by default, so removing CI's explicit enable-cache: false preserves the prior behavior. The action's retry wrapper and environment setup also support the CI Windows matrix.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[UltralyticsAssistant]

🎉 Thank you, @glenn-jocher, for this excellent contribution—and congratulations on the merge!

“Great things are done by a series of small things brought together.” — Vincent van Gogh

By standardizing UV setup through the shared setup-uv GitHub Action, this PR brings greater consistency to CI, publishing, and SBOM workflows while simplifying future maintenance. Your work strengthens the foundation that helps Ultralytics repositories move faster and more reliably. 🚀