Use setup-uv defaults for Python and the venv

[glenn-jocher]

Replaces actions/setup-python with ultralytics/actions/setup-uv. By default, that action now activates a venv on the newest Python preinstalled on the runner, with no Python download. Packages install into that venv, so --system is dropped. Jobs that pin a Python version keep the pin on setup-uv, which uses the preinstalled copy when the runner has one.

CI first ran against the setup-uv-defaults branch of ultralytics/actions#915. #915 is now merged (da5463a, released as 0.4.0), so setup-uv is back on @main, which carries the new defaults.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

The publish workflow now uses ultralytics/actions/setup-uv instead of actions/setup-python, and installs ultralytics-actions without the --system flag.

📊 Key Changes

• Removed the actions/setup-python step that selected Python 3.x.
• Added ultralytics/actions/setup-uv@main to set up Python and the virtual environment.
• Dropped --system from the uv pip install command.

🎯 Purpose & Impact

• In the publish workflow, ultralytics-actions installs into the environment activated by setup-uv rather than the system Python environment.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/template-rust 🚀 PR! This automated message confirms your contribution was received, and an Ultralytics engineer will assist with the 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-rust 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; the CLA check will comment with signing instructions if needed.
• ✅ 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}

Reviewed the publish workflow’s switch to setup-uv defaults and installation into the activated venv. The changed steps remain consistent with the workflow’s Python usage. LGTM.

Superseded by new review

[UltralyticsAssistant]

🔍 PR Review 2

_{Made with ❤️ by Ultralytics Actions}

Since review 1, no additional code changes are shown. The Python setup and venv installation changes remain sound, with no findings. LGTM.

[UltralyticsAssistant]

🎉 This PR has been merged—thank you, @glenn-jocher!

“Well done is better than well said.” — Benjamin Franklin

The publish workflow now installs ultralytics-actions into the environment set up by setup-uv.