fix(deps): update dependency ultralytics ( 8.4.62 → 8.4.67 ) - #410
Merged
Conversation
jazzlyn-bot
Bot
force-pushed
the
renovate/ultralytics-8.x
branch
from
June 10, 2026 14:44
fc16fef to
ebcb32b
Compare
jazzlyn-bot
Bot
force-pushed
the
renovate/ultralytics-8.x
branch
2 times, most recently
from
June 11, 2026 15:25
e5bcc8d to
162cf74
Compare
jazzlyn-bot
Bot
force-pushed
the
renovate/ultralytics-8.x
branch
from
June 12, 2026 02:06
162cf74 to
3085e79
Compare
jazzlyn-bot
Bot
force-pushed
the
renovate/ultralytics-8.x
branch
3 times, most recently
from
June 13, 2026 13:16
5db7a7d to
d88ff8c
Compare
| datasource | package | from | to | | ---------- | ----------- | ------ | ------ | | pypi | ultralytics | 8.4.62 | 8.4.67 |
jazzlyn-bot
Bot
force-pushed
the
renovate/ultralytics-8.x
branch
from
June 14, 2026 02:08
d88ff8c to
ef6d465
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==8.4.62→==8.4.67Release Notes
ultralytics/ultralytics (ultralytics)
v8.4.67: - Add opt-in weights_only model loading via ULTRALYTICS_SAFE_LOAD (#24829)Compare Source
🌟 Summary
v8.4.67 is a small but meaningful release focused on safer model loading 🔒, plus an important TT100K dataset label fix 🛣️ and a batch of documentation/link cleanups 📚.
📊 Key Changes
🔒 New opt-in safe model loading via
ULTRALYTICS_SAFE_LOAD(@glenn-jocher, PR #24829)ULTRALYTICS_SAFE_LOAD=true, that enables a safer way to load model checkpoints.weights_only=Truebehavior and only rebuilds known Ultralytics and PyTorch model classes from an automatically generated allow-list.SafeUnpicklerapproach.🛣️ TT100K dataset class list corrected to the official 221-category set (@glenn-jocher, PR #24718)
TT100K.yamldataset config had duplicated and incorrect class names.📘 Rust inference docs updated to
ultralytics-inference 0.0.21(@onuralpszr, PR #24825)🔗 Many documentation links were refreshed and corrected (@glenn-jocher, PR #24824 and #24817)
🎯 Purpose & Impact
🔐 Safer checkpoint loading for security-conscious users
♻️ Better future compatibility with PyTorch
weights_onlyloading by default.🚫 Less chance of silent dataset errors
🧰 Minimal disruption for most users
📚 Clearer onboarding and fewer broken docs
If you want, I can also provide a one-paragraph release note version or a developer-focused summary of v8.4.67.
What's Changed
Full Changelog: ultralytics/ultralytics@v8.4.66...v8.4.67
v8.4.66: - Addnvidia-ml-pyto pyproject.toml (#23922)Compare Source
🌟 Summary
Ultralytics v8.4.66 improves built-in NVIDIA GPU monitoring reliability 🔋, adds better semantic segmentation class filtering and metrics 🧠, and enhances CoreML semantic exports on iPhone with full-resolution outputs 📱.
📊 Key Changes
Main update: NVIDIA GPU monitoring is now more reliable 🚀
nvidia-ml-pywas added as a standard dependency by @glenn-jocher.Semantic segmentation got a meaningful feature upgrade 🎯
classesfilter now works properly for semantic segmentation during:single_cls=Truein semantic segmentation.Semantic segmentation metrics are more accurate 📈
CoreML semantic exports now keep full-resolution maps 📱✨
Updated iPhone CoreML benchmark docs 📊
TensorRT 11 export flow was simplified ⚙️
halfargument was removed from ONNX precision conversion.Documentation improvements across YOLO26 guides 📝
CI and packaging cleanup 🛠️
nvidia-ml-pyis now a standard dependency, extra manual installs were removed from CI and Docker setup.🎯 Purpose & Impact
More dependable GPU stats for users with NVIDIA hardware ✅
Users should see fewer issues with built-in GPU monitoring, logging, and hardware-aware utilities because the required NVIDIA package is now installed up front instead of handled on the fly.
Better usability for semantic segmentation workflows 🎨
If you work with semantic segmentation and only care about certain classes, filtering now behaves much more intuitively during prediction and evaluation.
More trustworthy segmentation metrics 📏
Reported semantic segmentation scores are now less misleading, especially on datasets where some classes are absent or filtered out.
Sharper CoreML semantic results on iPhone and Apple devices 🍎
Semantic masks should look much cleaner and less blocky, improving visual quality for mobile deployment.
Cleaner export experience for TensorRT 11 ⚡
Developers exporting models for NVIDIA deployment get a simpler and more maintainable precision conversion workflow.
Clearer docs for a broader audience 📚
New and experienced users alike should find YOLO26 testing, training, and deployment guidance easier to follow.
Overall, v8.4.66 is a practical quality-focused release: it strengthens GPU monitoring, improves semantic segmentation behavior, and brings better mobile export quality without changing the core user workflow.
What's Changed
classesfilter to semantic segmentation task by @lmycross in #24806nvidia-ml-pyto pyproject.toml by @glenn-jocher in #23922Full Changelog: ultralytics/ultralytics@v8.4.65...v8.4.66
v8.4.65: - QNN channel-last + semantic ArgMax performance improvements (#24790)Compare Source
🌟 Summary
v8.4.65 is mainly a mobile inference performance release 📱⚡, with the biggest upgrade improving QNN exports for Snapdragon NPUs and speeding up semantic segmentation outputs by moving costly work inside the model graph.
📊 Key Changes
🚀 Major QNN export performance upgrade in PR #24790 by @glenn-jocher
QNNModelinstead of fragile post-export graph editing.🧠 Semantic segmentation exports are much faster on-device
ClassMapModelwrapper handles this behavior during export.📱 Better mobile runtime compatibility
📉 Measured impact highlighted in docs
🛠️ RKNN export improvements
🐳 Docker build reliability improvements
📚 Docs and export guidance improvements
ultralytics-inferenceversion0.0.19.✅ CI and workflow fixes
main.🎯 Purpose & Impact
⚡ Faster mobile inference on Snapdragon devices
Users deploying YOLO on Qualcomm hardware should see lower overhead and better real-world efficiency, especially in camera-based apps where image buffers are already channel-last.
🧩 Less app-side postprocessing work
By returning semantic class maps directly from exported models, apps no longer need to spend as much CPU time decoding huge segmentation outputs.
📈 Better and more stable semantic segmentation performance
This is especially important for real-time mobile experiences, where unpredictable postprocessing delays can cause lag or jitter.
🔒 More robust export pipeline
Replacing manual ONNX graph surgery with clean wrapper modules makes exports easier to maintain and less error-prone over time.
📱🍎 Benefits extend beyond QNN
CoreML semantic exports also gain from the same in-graph class-map idea, so Apple-device deployment gets a speed boost too.
🛠️ Improved reliability for deployment workflows
Better RKNN testing, cleaner Docker builds, and more dependable docs publishing all reduce friction for developers working across edge and production environments.
👥 Broad user impact
In short: v8.4.65 is a strong deployment-focused release 🎉, with the standout improvement being faster, more hardware-friendly QNN exports and smarter semantic segmentation outputs for mobile AI.
What's Changed
Full Changelog: ultralytics/ultralytics@v8.4.64...v8.4.65
v8.4.64: - Tracker ReID ONNX encoders autodownload (#24774)Compare Source
🌟 Summary
Ultralytics
v8.4.64makes tracking easier and more reliable 🎯—especially with new auto-downloaded YOLO26 ReID ONNX encoders—while also improving QNN export, multi-GPU training stability, logging, and export robustness 🚀📊 Key Changes
Tracking got a major usability upgrade with auto-downloaded YOLO26 ReID ONNX encoders 🤖📦
You can now use built-in tracking ReID models like
yolo26n-reid.onnxthroughyolo26x-reid.onnxwithout manually downloading or exporting them first.Tracking ReID matching is more reliable when appearance features are missing 🔍
TrackTrack now treats missing embeddings as “unknown” instead of assuming they are bad matches, so it can fall back to motion cues more intelligently.
QNN export for Qualcomm devices was significantly improved 📱⚡
QNN models now export as a single self-contained
*_qnn.onnxfile instead of a folder, with metadata embedded inside. The release also fixes architecture mapping, improves backend loading compatibility, and updates quantization behavior for better Snapdragon deployment.YOLO26x distributed training stability was fixed 🧠🖥️
A DDP deadlock issue affecting some multi-GPU training runs was resolved by restoring handling for unused parameters in conditional branches.
MLflow failures no longer crash training 📉🛡️
If MLflow tracking setup or logging fails, training now continues instead of aborting the run.
TensorFlow export subprocess calls are safer 🔐
Edge TPU and TensorFlow.js export commands now avoid shell-based path handling issues, reducing problems with unusual file paths and improving security.
Progress/logging output was cleaned up 🖥️✨
Fixed premature
100%progress display and console log duplication issues, especially useful in platform or remote logging environments.Version checking is more accurate ✅
parse_version()now consistently returns 3-part version tuples, fixing incorrect version comparisons like6.0vs6.0.0.FP16 quantization/export reliability was improved ⚙️
ONNX mixed-precision conversion now uses the correct input name and sample input shape, helping TensorRT/ModelOpt workflows work more consistently.
Docs were refreshed across several areas 📘
Updates include clearer tracking/ReID docs, QNN docs, Conda install guidance, hyperparameter tuning explanations, TrackZone behavior, custom trainer checkpoint loading, OpenVINO benchmark references, and terminal visualization guidance.
🎯 Purpose & Impact
Easier multi-object tracking setup 🚀
The headline change removes a common setup headache: users can now enable tracking ReID with ready-made YOLO26 ONNX encoders directly, making advanced tracking more accessible to both beginners and production teams.
Better tracking quality in difficult scenes 🎥
The ReID fallback improvement should reduce bad associations when objects are briefly occluded or appearance features are unavailable.
Simpler Qualcomm deployment 📱
QNN export is now easier to manage and deploy thanks to the single-file output format and improved compatibility across Snapdragon targets.
More dependable training at scale 🖥️
Teams training larger YOLO26 models on multiple GPUs should see fewer hangs and more stable runs.
Fewer pipeline interruptions 🛠️
MLflow and export-related fixes help ensure optional integrations do not stop core training or deployment workflows.
Cleaner user experience ✨
Console logging and progress bar fixes make training output easier to trust and monitor, especially in shared platforms and dashboards.
Lower friction for installation and documentation 📚
Updated guides make setup, tuning, export, and custom workflows easier to understand and reproduce.
In short,
v8.4.64is a tracking-focused quality-of-life release with especially strong benefits for users working with YOLO26 tracking, Qualcomm QNN deployment, and stable training/export pipelines 🚀What's Changed
parse_versionto always return a 3-tuple by @bujna94 in #24680openvino==2026.2.0by @lakshanthad in #24691New Contributors
Full Changelog: ultralytics/ultralytics@v8.4.63...v8.4.64
v8.4.63: - NVIDIA TensorRT 11 support with ModelOpt FP16 and INT8 quantization (#24735)Compare Source
🌟 Summary
🚀 Ultralytics v8.4.63 mainly adds TensorRT 11 export support with FP16 and INT8 quantization via NVIDIA ModelOpt, while also expanding built-in multi-object tracking with several new tracker options and improving reliability, performance, and docs.
📊 Key Changes
🧠 Major export upgrade: TensorRT 11 support
fp32fp16int8⚡ Better quantization workflow for modern NVIDIA deployment
🎯 Big tracking expansion: 4 new built-in trackers
ocsort.yamldeepocsort.yamlfasttrack.yamltracktrack.yaml🏃 Tracking docs and selection guidance improved
📹 Video stream loading is safer
⚡ AI Gym pose workflow is faster
🧪 Validation mixed precision handling simplified
📝 Documentation improvements
🎯 Purpose & Impact
🚀 TensorRT 11 users can export again
⚙️ Future-proofs NVIDIA deployment
💾 Smaller, faster engines remain accessible
📦 Dynamic INT8 export support is especially useful
👀 Tracking becomes more flexible for real-world scenarios
🔒 More stable long-running applications
⚡ Small but meaningful performance wins
Overall, v8.4.63 is a strong deployment-focused release 📦—with the headline improvement being restored and modernized TensorRT 11 export support, plus a major boost to tracking capabilities and several reliability/performance refinements.
What's Changed
isolated_modelandisolated_task_modelintoisolated_model_pathby @Laughing-q in #24742Full Changelog: ultralytics/ultralytics@v8.4.62...v8.4.63
Configuration
📅 Schedule: (in timezone Europe/Vienna)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.