fix(deps): update dependency ultralytics ( 8.4.57 → 8.4.58 ) - #400

v8.4.58: - ultralytics 8.4.58 Isolated CI export environments (#​24649)

Compare Source

🌟 Summary

Ultralytics v8.4.58 is mainly a reliability-focused release 🛠️ that improves how export formats are tested in CI, making model export support more stable, isolated, and easier to maintain—especially for specialized formats.

📊 Key Changes

• 🚦 Export testing was redesigned around isolated environments

  • The biggest update in this release, from PR #​24649 by @​glenn-jocher, separates export tests into dedicated environments instead of testing everything in one shared CI setup.
  • This is especially important for formats with conflicting dependencies, such as TensorFlow, CoreML, MNN, NCNN, ExecuTorch, IMX, RKNN, Axelera, and DEEPX.

• 🧩 Each export format now declares its own environment

  • The internal export_formats() registry now includes environment metadata for every export target.
  • This lets the test system know exactly where each export should run.

• 🧪 New --export-env test selection

  • CI no longer relies on manually skipping individual export tests.
  • Instead, tests are selected by export environment, which is cleaner and much less error-prone.

• ⚙️ New automated isolated export job

  • A new IsolatedExports CI workflow now builds dedicated virtual environments and runs smoke tests plus export tests inside them.
  • This replaces the older shell-script-based slow test coordination.

• 📦 Export dependencies were split into smaller groups

  • The release breaks the old monolithic export dependencies into targeted extras like:
    • export-base
    • export-tensorflow
    • export-coreml
    • export-executorch
    • export-deepx
    • export-legacy-torch
  • This keeps base installs leaner and avoids pulling in heavy packages unless they are truly needed.

• ✅ Added checks to prevent export registry mistakes

  • New tests ensure:
    • every export environment has a smoke test
    • every export format points to a valid registered environment

• 🤖 RKNN export test added

  • A dedicated test for RKNN export was added, improving coverage for Rockchip deployment workflows.

• 🐳 Docker cleanup improved

  • Export Docker images now clean caches more aggressively, helping reduce leftover build artifacts and keeping images/workflows tidier.

🎯 Purpose & Impact

• 🔒 More reliable exports

  • Users who export YOLO models to many different formats should see fewer CI-related regressions slipping through.
  • In simple terms: export support is being tested in a way that better matches real-world usage.

• 🚀 Faster and leaner development workflows

  • Base CI jobs now install a smaller export stack, which should reduce unnecessary dependency load and make routine testing more efficient.

• 🧹 Simpler maintenance for the Ultralytics team

  • The new registry-driven setup replaces fragile manual skip lists and shell workarounds.
  • That means adding or maintaining export formats should be easier going forward.

• 🌍 Better support for specialized deployment targets

  • Formats used for edge and hardware-specific deployment—like IMX, RKNN, Axelera, DEEPX, and ExecuTorch—now get clearer, dedicated validation paths.

• 📌 No major new model architecture in this release

  • This release does not introduce a new YOLO model or major end-user training feature.
  • Its main impact is improved stability, compatibility, and confidence in exporting existing models for deployment.

• 🧠 Good news for production users

  • If you depend on exporting YOLO models to mobile, embedded, browser, or accelerator-specific formats, this release reduces the chance that one format breaks another behind the scenes.

If you'd like, I can also turn this into a shorter changelog-style summary or a more technical developer-focused breakdown.

What's Changed

• ultralytics 8.4.58 Isolated CI export environments by @​glenn-jocher in #​24649

Full Changelog: ultralytics/ultralytics@v8.4.57...v8.4.58