package: 📦 version bump to ultralytics-inference 0.0.15

[onuralpszr]

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Minor release update to ultralytics-inference 0.0.15 that improves app naming consistency across the CLI, viewer window, and documentation ✨

📊 Key Changes

• Bumped the crate version from 0.0.14 to 0.0.15 📦
• Added a new shared DISPLAY_NAME constant in src/lib.rs for the app name: Ultralytics Inference 🏷️
• Updated CLI output in src/cli/predict.rs to print Ultralytics Inference instead of the shorter Ultralytics name 🖥️
• Updated the viewer window title to use the same shared display name for consistency 👀
• Refreshed README.md examples and dependency instructions to match version 0.0.15 and the new product naming 📝
• Included the corresponding lockfile update in Cargo.lock 🔒

🎯 Purpose & Impact

• Improves branding consistency across the Rust inference package, making logs, windows, and docs easier to recognize ✅
• Reduces hardcoded naming in multiple places by centralizing the display name, which makes future maintenance simpler 🛠️
• Helps users avoid confusion when comparing terminal output with documentation examples 📚
• No major behavioral or model inference changes are introduced, so this appears to be a low-risk polish and release-management update 🚀

📋 Skipped 1 file (lock files, generated, images, etc.)

• Cargo.lock

[UltralyticsAssistant]

👋 Hello @onuralpszr, thank you for submitting a ultralytics/inference 🚀 PR! This is an automated message to help with review readiness; an engineer will assist you shortly. Please review the checklist below to help ensure a 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/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}

Clean, low-risk release PR. The version bumps are consistent across Cargo.toml, Cargo.lock, and README.md, and centralizing the display string via DISPLAY_NAME improves branding consistency without introducing any obvious functional or maintainability issues in the changed lines.

📋 Skipped 1 file (lock files, generated, images, etc.)

• Cargo.lock

[codecov]

Codecov Report

❌ Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
src/cli/predict.rs	0.00%	2 Missing ⚠️

📢 Thoughts on this report? Let us know!

[UltralyticsAssistant]

🎉 Excited to see this merged — thank you @onuralpszr!

As Aristotle said, “Excellence is not an act, but a habit.” This update is a great example of that: small, thoughtful improvements like centralizing DISPLAY_NAME and aligning the CLI, viewer, and docs help make ultralytics-inference feel more polished, consistent, and easier to maintain.

Really appreciate the attention to detail here, especially for a low-risk release improvement that strengthens the overall user experience.