Fix invalid setup-uv action version

[glenn-jocher]

Summary

• change astral-sh/setup-uv from @v8 to @v7 in release workflows
• fix the workflow reference to an action version that exists

Testing

• rg -n --hidden --no-ignore 'astral-sh/setup-uv@v8' /Users/glennjocher/PycharmProjects

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

🔧 This PR updates the GitHub publish workflow to use astral-sh/setup-uv@v7 instead of @v8, likely to improve workflow stability and compatibility.

📊 Key Changes

• Replaced astral-sh/setup-uv@v8 with astral-sh/setup-uv@v7 in .github/workflows/publish.yml.
• Applied this change in all affected publish workflow jobs, including:
  • the PyPI check/install step
  • the package build step
  • the SBOM-related environment setup step
• No application code or package logic was changed; this is a CI/CD workflow-only update. 🛠️

🎯 Purpose & Impact

• Helps avoid issues introduced by setup-uv@v8, likely by reverting to a more reliable or compatible version. ✅
• Improves the consistency of automated publishing, building, and SBOM generation in GitHub Actions.
• Reduces the risk of CI failures during release workflows, which can make package publishing more dependable for maintainers. 🚀
• Since this only affects automation infrastructure, end users should not see any direct product changes.

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting a ultralytics/mkdocs 🚀 PR! This is an automated message to help with review, and an engineer will assist you shortly. Please review the checklist below to help ensure smooth integration. 😊

• ✅ 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}

This is a clean, low-risk workflow fix. The change is narrowly scoped to the three invalid astral-sh/setup-uv references and I don't see any bugs, regressions, or maintainability issues in the diff provided.

[UltralyticsAssistant]

Thrilled to see this merged, @glenn-jocher — thank you for the thoughtful CI refinement here! As Benjamin Franklin said, “An ounce of prevention is worth a pound of cure,” and this rollback to setup-uv@v7 is a perfect example: a small workflow change that helps keep publishing, builds, and SBOM generation stable and dependable. Really appreciate the care you put into strengthening the release pipeline behind the scenes. 🙌