Document cuda-preprocess in the library feature table

[onuralpszr]

The cuda-preprocess feature is listed in Cargo.toml, README.md, and README.zh-CN.md, but was missing from the feature table in the crate docs.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Updated the crate documentation feature table to include the existing cuda-preprocess feature and describe its GPU preprocessing capability.

📊 Key Changes

• Added cuda-preprocess to the feature table in src/lib.rs.
• Documented it as providing GPU preprocessing with zero-copy TensorRT input.
• No code or feature configuration was changed.

🎯 Purpose & Impact

• The crate documentation now matches the feature listings already present in Cargo.toml, README.md, and README.zh-CN.md.
• No user-facing behavior change.

[UltralyticsAssistant]

👋 Hello @onuralpszr, thank you for submitting a ultralytics/inference 🚀 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/inference 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}

Reviewed the src/lib.rs crate documentation feature table and verified the cuda-preprocess feature name and description against Cargo.toml, README files, and existing CUDA documentation. The change is accurate, minimal, and introduces no behavioral risk. LGTM.

[UltralyticsAssistant]

🎉 This PR has been merged—thank you @onuralpszr!

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

Your focused documentation update brings the cuda-preprocess feature table in src/lib.rs into alignment with the existing crate configuration and README documentation, clearly describing GPU preprocessing with zero-copy TensorRT input without changing user-facing behavior.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!