fix(deps): update dependency ultralytics ( 8.4.102 → 8.4.104 ) - #463
Merged
Conversation
jazzlyn-bot
Bot
force-pushed
the
renovate/ultralytics-8.x
branch
from
July 22, 2026 01:14
fa267c8 to
ca07bd1
Compare
| datasource | package | from | to | | ---------- | ----------- | ------- | ------- | | pypi | ultralytics | 8.4.102 | 8.4.104 |
jazzlyn-bot
Bot
force-pushed
the
renovate/ultralytics-8.x
branch
from
July 22, 2026 13:14
ca07bd1 to
0f39fdf
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.102→==8.4.104Release Notes
ultralytics/ultralytics (ultralytics)
v8.4.104: - New YOLO26-Depth monocular depth estimation task (#25065)Compare Source
🌟 Summary
YOLO26 gains a complete monocular depth estimation task, enabling per-pixel distance prediction, training, validation, visualization, calibration, and deployment alongside existing Ultralytics tasks. 🌍📐
📊 Key Changes
New YOLO26-Depth model family 🤖
yolo26n-depth,yolo26s-depth,yolo26m-depth,yolo26l-depth, andyolo26x-depth.Depth is now a first-class Ultralytics task 🆕
yolo depth train yolo depth val yolo depth predict yolo exportModelAPI, including prediction, training, validation, export, andmodel.calibrate().Improved depth training and evaluation 📊
Depth-aware data pipeline 🗂️
.npyfloat32 depth-map loading.Large dataset and benchmark support 🌐
Depth visualization and results support 🎨
DepthMapresults, depth heatmap plotting, depth-aware result summaries, and access throughresult.depth.data..cpu()and.numpy()workflows.Export and deployment support 🚀
opsetandworkspacearguments.More reliable training logs 🧾
l1_lossasdfl_losswhen DFL is not used.Performance and reliability improvements ⚡
log_softmaxonce instead of twice, improving the DFL loss path by approximately 1.5–1.75× in benchmarks.Export, dataset, and workflow fixes 🛠️
Pathexport arguments to strings, preventing exported ONNX metadata from failing to reload.safe_download(..., delete=True).🎯 Purpose & Impact
Expands YOLO26 beyond object recognition 🌟
Users can now infer scene geometry and approximate camera-to-surface distances from a single RGB image, supporting robotics, navigation, AR/VR, 3D reconstruction, and spatial awareness applications.
Handles a wider range of environments 🏠🚗
The unbounded log-depth design avoids a fixed short-range ceiling, making the models better suited to both indoor scenes and long-range outdoor driving data such as KITTI.
Simplifies end-to-end development ✅
Depth estimation uses the same familiar Ultralytics workflow for dataset preparation, training, validation, prediction, export, and Python integration.
Improves custom-dataset adaptation 🎯
Users can fine-tune pretrained YOLO26-Depth models and calibrate absolute depth scale without retraining the network, helping adapt predictions to a particular camera or environment.
Makes deployments more dependable 🔒
Dynamic export shapes, corrected metadata serialization, more accurate TensorRT documentation, and safer archive handling reduce friction when moving models into production.
Benefits existing tasks as well ⚙️
The loss-dictionary refactor, DFL optimization, assigner optimization, semantic-mask caching, and CI robustness fixes improve maintainability, logging accuracy, training speed, and reliability across the broader Ultralytics framework.
For production workflows, YOLO26 remains the recommended latest stable model family. Users who prefer managed annotation, training, and deployment can also use the Ultralytics Platform.
What's Changed
Full Changelog: ultralytics/ultralytics@v8.4.103...v8.4.104
v8.4.103: - Prevent training from ending during warmup (#25321)Compare Source
🌟 Summary
v8.4.103 improves training reliability, result handling, deployment workflows, and documentation—most importantly ensuring warmup finishes on schedule so short training runs reach their intended learning-rate behavior. 🚀
📊 Key Changes
Training warmup no longer consumes entire short runs 🎯
warmup_epochsis now treated as a true epoch count rather than being forced to at least 100 iterations.More accurate validation and experiment reporting 📈
Improved model construction and performance ⚡
ModelEMAupdates with batched PyTorch operations where supported.More robust results and mask processing 🖼️
Resultsmethods such asplot(),save_txt(),save_crop(),summary(), andverbose()now work correctly with NumPy-backed results fromResults.numpy().Safer and clearer exports 🔧
opsetargument.Expanded Platform and API capabilities ☁️
latesttags.--devicereservations for more reliable access across host daemon reloads.Documentation and workflow improvements 📚
actions/setup-python@v7.🎯 Purpose & Impact
What's Changed
opsetargument from Hailo export by @lakshanthad in #25305ModelEMAupdate with batched_foreach_lerp_by @raimbekovm in #25315process_maskby @JESUSROYETH in #25298ncby @JESUSROYETH in #25297Full Changelog: ultralytics/ultralytics@v8.4.102...v8.4.103
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.