Pin beaufulsoup4<=4.12.3

[Laughing-q]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated plugin version and constrained a dependency to ensure stability and compatibility.

📊 Key Changes

• Bumped plugin version from 0.1.16 to 0.1.17.
• Added an upper bound (<=4.12.3) to the BeautifulSoup (beautifulsoup4) dependency.

🎯 Purpose & Impact

• Version update ensures users can identify the latest changes and fixes. 📈
• Dependency constraint prevents issues with potential breaking changes in newer BeautifulSoup releases, ensuring a smoother experience for users. 🛠️

[UltralyticsAssistant]

👋 Hello @Laughing-q, thank you for submitting an ultralytics/mkdocs 🚀 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/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

We noticed your PR involves pinning the beautifulsoup4 dependency. Please make sure your changes are fully justified and account for potential downstream effects on compatibility. If applicable, provide any additional context or examples that might explain the implications and necessity of this update.

Thank you again for your contribution! An Ultralytics engineer will review your PR shortly. In the meantime, for more guidance, please refer to our Contributing Guide. Don’t hesitate to leave a comment if you have any questions. We’re here to help! 🚀✨

[glenn-jocher]

@Laughing-q looks good! I'll increment the version to publish a new package.

[UltralyticsAssistant]

🚀 Amazing work, @Laughing-q and @glenn-jocher! Your dedication to keeping things stable and forward-compatible shines through in this PR. 🌟

As Benjamin Franklin once said, "An ounce of prevention is worth a pound of cure." Constraining dependencies and updating versions might not always seem glamorous, but it’s the kind of foresight that ensures our tools stay reliable and user-friendly. 💡

Big thanks for this impactful contribution—it’s a small change with a powerful ripple effect across the community. Keep up the fantastic work! 🙌