SBOM uv sync fix

[glenn-jocher]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

No code or content changes were made in this PR — it’s an empty diff.

📊 Key Changes

• No files modified, added, or removed.
• No documentation, configuration, or build updates included.

🎯 Purpose & Impact

• Likely a placeholder, sync, or CI re-run PR with no user-facing impact.
• No changes to documentation behavior, site content, or developer workflow. ✅

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting an ultralytics/mkdocs 🚀 PR! This is an automated response to help streamline reviews. An Ultralytics engineer will also assist you shortly.

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

If this PR addresses a bug and there are runtime or CI failures related to the change, please include a Minimum Reproducible Example (MRE) demonstrating the issue so we can verify the fix quickly.

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]

Merged with gratitude—thank you, @glenn-jocher! As Leonardo da Vinci said, “Simplicity is the ultimate sophistication.” Even an empty diff can keep our workflows clean and our momentum steady. Your steady stewardship keeps Ultralytics docs humming and the path clear for future improvements. Appreciate you!