Use shared setup-uv action everywhere

[glenn-jocher]

Summary

• replace all 3 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: 3 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

Standardizes uv setup in the publishing workflow by using Ultralytics’ shared GitHub Action. 🔧

📊 Key Changes

• Replaced astral-sh/setup-uv@v7 with ultralytics/actions/setup-uv@main.
• Applied the change across publishing, package-building, and SBOM-generation jobs.
• Kept the existing Python, build, and dependency-installation steps unchanged.

🎯 Purpose & Impact

• Centralizes uv setup and maintenance within Ultralytics’ shared actions. 🛠️
• Improves consistency across Ultralytics repositories and workflows.
• Reduces reliance on an external setup action, potentially simplifying future updates and troubleshooting.
• Publishing behavior should remain unchanged for users and package consumers. ✅

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/mkdocs 🚀 PR! This is an automated review message, and an engineer will assist as needed. 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/mkdocs 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}

The workflow change consistently adopts the shared setup action, but the new mutable branch references introduce a supply-chain risk in privileged publishing jobs. Pin the action revision before merging.

💬 Posted 1 inline comment

[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

Standardizing uv setup through Ultralytics’ shared GitHub Action strengthens consistency across publishing, package-building, and SBOM workflows while simplifying future maintenance. Your careful change helps keep our release infrastructure reliable and aligned across repositories. 🙌