Skip to content

fix(deps): update dependency ultralytics ( 8.4.68 → 8.4.70 ) - #417

Merged
jazzlyn-bot[bot] merged 1 commit into
mainfrom
renovate/ultralytics-8.x
Jun 18, 2026
Merged

fix(deps): update dependency ultralytics ( 8.4.68 → 8.4.70 )#417
jazzlyn-bot[bot] merged 1 commit into
mainfrom
renovate/ultralytics-8.x

Conversation

@jazzlyn-bot

@jazzlyn-bot jazzlyn-bot Bot commented Jun 17, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change OpenSSF
ultralytics (changelog) project.dependencies patch ==8.4.68==8.4.70 OpenSSF Scorecard

Release Notes

ultralytics/ultralytics (ultralytics)

v8.4.70: - Fix DDP AMP broadcast state synchronization (#​24810)

Compare Source

🌟 Summary

v8.4.70 is a reliability-focused release 🛠️ led by an important fix for multi-GPU training, plus safer checkpoint loading, a plotting fix for segmentation results, and clearer docs around YOLO26 heatmaps, training outputs, and deployment 📚

📊 Key Changes

  • 🐛 Fixed DDP AMP synchronization in multi-GPU training in PR #​24810 by @​LZ-QWQ

    • This is the main update in the release.
    • It fixes a bug where AMP mixed-precision training could be disabled on one GPU rank but remain enabled on others during Distributed Data Parallel training.
    • After the fix, all ranks now correctly share the same AMP setting.
  • Safer checkpoint loading with clearer errors in PR #​24857 by @​glenn-jocher

    • Ultralytics now gives a clear, user-friendly error when loading unsupported checkpoint formats, such as plain state_dict files or some older YOLOv5-style module references.
    • This replaces confusing crashes like AttributeError or KeyError.
  • 🎨 Fixed Results.plot() for masks-only outputs in PR #​24635 by @​ahmet-f-gumustas

    • Segmentation results that contain masks but no bounding boxes no longer crash during plotting.
    • This helps users working with custom or partial result objects.
  • 🔥 Heatmaps guide was rewritten around real tracking use cases in PR #​24815 by @​raimbekovm

    • The documentation now better explains that YOLO26 heatmaps are for object tracking over video, not just generic data visualization.
    • It clarifies real-world uses like traffic flow, crowd movement, and region-based counting.
  • 📁 Documented the save_dir training argument in PR #​24831 by @​raimbekovm

    • Users can now more easily understand how to send training outputs to an exact folder without auto-increment behavior.
  • 🧩 Small quality-of-life fixes in docs and config

🎯 Purpose & Impact

  • 🚀 More reliable distributed training

    • The AMP/DDP fix is especially important for users training on multiple GPUs.
    • It prevents inconsistent precision behavior across devices, which could otherwise lead to unstable training, debugging headaches, or hard-to-trace performance issues.
  • 🛡️ Fewer cryptic failures

    • The checkpoint-loading improvements make model-loading problems much easier to understand.
    • This is especially helpful for users migrating from older formats or using custom-saved weights.
  • 🎯 Better support for segmentation workflows

    • The plotting fix makes Ultralytics more robust for segmentation-only results and edge cases.
  • 📚 Clearer guidance for real-world YOLO26 usage

    • The heatmaps documentation update makes it easier for a broad audience to understand how YOLO26 can be used for video analytics, such as retail, transportation, and crowd analysis.
  • ⚙️ Smoother day-to-day experience

    • While many of the remaining changes are documentation and maintenance updates, they reduce confusion, improve discoverability, and make the platform easier to use overall.

In short: v8.4.70 is mainly a stability and usability release ✅ with the standout improvement being a critical fix for consistent AMP behavior in distributed multi-GPU training.

What's Changed

New Contributors

Full Changelog: ultralytics/ultralytics@v8.4.69...v8.4.70

v8.4.69: - Allow safe load of checkpoints with getattr (#​24852)

Compare Source

🌟 Summary

Ultralytics v8.4.69 is a small but important reliability update 🔒 that improves safe checkpoint loading, especially for some YOLO11 and YOLOv8 segmentation, pose, OBB, and classification models.

📊 Key Changes

  • 🔐 Safe loading now supports certain getattr references inside checkpoints

    • Some model checkpoints store internal references using getattr, which were previously blocked when safe loading was enabled.
    • This update allows those checkpoints to load correctly without turning off the safety mechanism.
  • 🤖 Fixes safe loading for several model types

    • Affects checkpoints used by:
      • YOLO11 segmentation
      • YOLO11 classification
      • YOLO11 pose
      • YOLO11 OBB
      • Similar affected YOLOv8 checkpoint variants
  • 🧩 Added restricted support for enum-based references

    • The safe loader now understands certain enum values used in saved checkpoints, such as interpolation settings.
  • 🛡️ Still keeps the load process restricted

    • Instead of broadly allowing any getattr use, the change adds a limited internal handler that only permits approved cases.
    • This helps preserve security while improving compatibility.
  • 📦 Version bump

    • Package version updated from 8.4.68 to 8.4.69.

🎯 Purpose & Impact

  • Fewer loading/export errors with safe mode enabled

    • Users working with ULTRALYTICS_SAFE_LOAD=1 should now be able to load and export affected checkpoints more smoothly.
  • 🔒 Better security without losing usability

    • The goal is to keep safe loading strict, while avoiding unnecessary failures for legitimate Ultralytics model files.
  • 🚀 Improves deployment and export workflows

    • This is especially helpful for users exporting models in secure or controlled environments, where safe loading is preferred or required.
  • 👥 Good quality-of-life fix for everyday users

    • If you use pretrained segmentation, pose, OBB, or classification checkpoints, this update can reduce friction without changing your training or inference workflow.
  • 📌 Low-risk, high-value release

    • There are no major new model architectures or training features here; this release is mainly a stability and compatibility fix with practical impact.

If helpful, I can also provide a one-paragraph changelog version or a more technical developer-focused summary.

What's Changed

Full Changelog: ultralytics/ultralytics@v8.4.68...v8.4.69


Configuration

📅 Schedule: (in timezone Europe/Vienna)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate.

@jazzlyn-bot
jazzlyn-bot Bot force-pushed the renovate/ultralytics-8.x branch from 697ee57 to 66a8e00 Compare June 17, 2026 14:43
@jazzlyn-bot jazzlyn-bot Bot changed the title fix(deps): update dependency ultralytics ( 8.4.68 → 8.4.69 ) fix(deps): update dependency ultralytics ( 8.4.68 → 8.4.70 ) Jun 17, 2026
| datasource | package     | from   | to     |
| ---------- | ----------- | ------ | ------ |
| pypi       | ultralytics | 8.4.68 | 8.4.70 |
@jazzlyn-bot
jazzlyn-bot Bot force-pushed the renovate/ultralytics-8.x branch from 66a8e00 to 4733848 Compare June 17, 2026 14:43
@jazzlyn-bot
jazzlyn-bot Bot merged commit 955fec0 into main Jun 18, 2026
1 check passed
@jazzlyn-bot
jazzlyn-bot Bot deleted the renovate/ultralytics-8.x branch June 18, 2026 02:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants