Use shared setup-uv action everywhere

[glenn-jocher]

Summary

• replace all 2 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: 2 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 GitHub Actions workflows to use Ultralytics’ shared setup-uv action. ⚙️

📊 Key Changes

• Replaced astral-sh/setup-uv@v6 with ultralytics/actions/setup-uv@main in:
  • Continuous integration (ci.yml)
  • Push workflow (push.yml)
• Kept the existing Python setup and dependency installation steps unchanged.

🎯 Purpose & Impact

• 🧩 Standardizes uv environment setup across Ultralytics repositories.
• 🔄 Centralizes workflow maintenance in the shared Ultralytics actions repository.
• ✅ Helps keep CI and push workflows consistent and easier to update.
• 🚀 No direct changes to application behavior; the impact is limited to development and automation workflows.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/replicate 🚀 PR! This automated review has been added, and an engineer will assist with any follow-up. 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/replicate 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. Both workflows correctly replace the direct uv setup action with the shared Ultralytics action, and the existing Python setup remains compatible with the shared action’s optional inputs.

[UltralyticsAssistant]

🎉 Thank you @glenn-jocher for this valuable 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 Ultralytics action, this PR makes our CI and push workflows more consistent, maintainable, and easier to improve across repositories. We appreciate your continued efforts to strengthen the development experience!