🚀 Release v0.0.26: LiteRT.js backend documentation fixes and file/blob support

[onuralpszr]

Version bump to 0.0.26. Highlights since 0.0.25:

• New optional LiteRT.js backend: run Ultralytics .tflite exports in the browser, auto-detected from the model, on WebGPU where supported.
• YOLO.load now accepts a Blob/File, so a dropped or picked model loads directly.
• Bumped miniz_oxide to 0.9.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

📦 This PR is a version bump release that updates ultralytics-inference and related packages from 0.0.25 to 0.0.26, with matching documentation and package metadata updates.

📊 Key Changes

• ⬆️ Updated the core Rust crate version in Cargo.toml from 0.0.25 to 0.0.26.
• 🌐 Updated the web/WASM package version in crates/web/Cargo.toml to 0.0.26.
• 📦 Updated the npm package @ultralytics/yolo in web/package.json to 0.0.26.
• 📝 Refreshed README examples and installation snippets in both English and Chinese to reference 0.0.26.
• ⚙️ Updated CUDA setup documentation so dependency examples now point to 0.0.26.
• 🔒 Regenerated lockfiles (Cargo.lock and web/package-lock.json) to match the new release state.

🎯 Purpose & Impact

• 🚀 Prepares and publishes a new 0.0.26 release across Rust and web packages.
• ✅ Keeps versioning consistent across code, docs, CLI output, and package managers.
• 📚 Reduces user confusion by ensuring installation instructions match the latest release.
• 🧩 Makes it easier for developers to adopt the newest package version in Rust, CUDA, and browser-based workflows.
• ⚠️ This PR does not introduce visible feature changes or behavior changes by itself; its main impact is release packaging and documentation alignment.

📋 Skipped 2 files (lock files, generated, images, etc.)

• Cargo.lock
• web/package-lock.json

[UltralyticsAssistant]

👋 Hello @onuralpszr, thank you for submitting a ultralytics/inference 🚀 PR! This is an automated message to help streamline review, and an engineer will assist you shortly. Please review the checklist below to ensure a smooth integration of your version bump PR ✨

• ✅ 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 version bump PR. The crate, web package, lockfiles, and documentation examples are updated consistently from 0.0.25 to 0.0.26, and I didn't find any actionable issues in the changed lines.

📋 Skipped 2 files (lock files, generated, images, etc.)

• Cargo.lock
• web/package-lock.json

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[UltralyticsAssistant]

Merged! 🎉 Thanks, @onuralpszr, for keeping ultralytics-inference 0.0.26 aligned across Rust, web, npm, docs, and lockfiles.

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

This release bump is a great example of that: careful version consistency and documentation updates make adoption smoother, reduce confusion, and help ensure a reliable experience for everyone using the project. Really appreciate the clean and thorough contribution.