Use shared setup-uv action everywhere

[glenn-jocher]

Summary

• replace both Astral uv setup steps with the shared retried owner
• preserve the existing link-check and release workflows

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

Deleted: two direct astral-sh/setup-uv dependencies.

Validation

• zero uses: astral-sh/setup-uv occurrences
• actionlint on both changed workflows
• git diff --check
• shared owner passed Windows, Ubuntu, and macOS CI in Support retried uv setup on Windows actions#819

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

🔧 Updated documentation workflows to use Ultralytics’ shared setup-uv GitHub Action.

📊 Key Changes

• Replaced astral-sh/setup-uv@v7 with ultralytics/actions/setup-uv@main in:
  • The link-checking workflow.
  • The tag-management workflow.
• Kept the existing Python setup and dependency installation steps unchanged.

🎯 Purpose & Impact

• ✅ Centralizes uv setup through Ultralytics’ shared Actions repository.
• 🔄 Makes workflow maintenance and future updates easier across projects.
• 🚀 Ensures link checks and tag automation use a consistent internal setup.
• ⚠️ Because the action tracks @main, workflow behavior may change when the shared action is updated.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/docs 🚀 PR! 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/docs 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. This is an automated message, and an engineer will assist if needed. Thank you for contributing to Ultralytics! 🚀

[UltralyticsAssistant]

🔍 PR Review

_{Made with ❤️ by Ultralytics Actions}

Clean change. Both workflows already provision Python before invoking the shared setup-uv action, and the downstream uv pip install --system commands remain compatible with the shared action's default behavior.

[UltralyticsAssistant]

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

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

By switching the documentation workflows to Ultralytics’ shared setup-uv action while preserving the existing setup steps, this PR improves consistency, simplifies maintenance, and strengthens our link-checking and tag-management automation. Your thoughtful work helps keep the project reliable and scalable—thank you!