# New Release: Ultralytics v8.4.58

**URL:** <https://community.ultralytics.com/t/new-release-ultralytics-v8-4-58/2018>\
**Category:** Discussion\
**Tags:** releases, announcements, ultralytics-official\
**Created:** [May 31, 2026, 1:33pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-4-58/2018 "2026-05-31T13:33:52Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![glenn-jocher](https://sea1.discourse-cdn.com/flex001/user_avatar/community.ultralytics.com/glenn-jocher/32/83_2.png) [@glenn-jocher](https://community.ultralytics.com/u/glenn-jocher)\
**Post date:** [May 31, 2026, 1:33pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-4-58/2018/1 "2026-05-31T13:33:52Z")

</div>

# Ultralytics v8.4.58 is out 🚀

We’ve released **Ultralytics `v8.4.58`** , a reliability-focused update that makes **model export testing more stable, isolated, and maintainable** across a wide range of deployment targets. While this release does not introduce a new model architecture, it delivers important behind-the-scenes improvements that strengthen export support for Ultralytics YOLO users working across mobile, embedded, browser, and accelerator-specific environments.

If you rely on exporting models for deployment, this release should give you more confidence that formats are being tested in ways that better reflect real-world usage ✅

## Quick Summary

- 🛠 Redesigned export testing around **isolated environments**
- 🧩 Added **environment metadata** to each export format
- 🧪 Introduced **`--export-env`** for cleaner test selection
- ⚙ Added a new **`IsolatedExports`** CI workflow
- 📦 Split export dependencies into **smaller targeted extras**
- ✅ Added validation checks for export registry consistency
- 🤖 Added **RKNN export test** coverage
- 🐳 Improved Docker cleanup for export images

You can explore the full release on the [Ultralytics `v8.4.58` release page](https://github.com/ultralytics/ultralytics/releases/tag/v8.4.58) and review all changes in the [full changelog from `v8.4.57` to `v8.4.58`](https://github.com/ultralytics/ultralytics/compare/v8.4.57...v8.4.58).

## New Features

### 🚦 Isolated export testing in CI

The biggest change in this release is that export tests are now organized into **dedicated environments** instead of being run together in one shared CI setup.

This work came in [PR #24649](https://github.com/ultralytics/ultralytics/pull/24649) by [@glenn-jocher](https://github.com/glenn-jocher).

Why this matters:

- Reduces dependency conflicts between export backends
- Better reflects how users actually install and use specific export targets
- Makes specialized formats easier to test and maintain over time

This is especially helpful for formats with conflicting or heavyweight dependencies, including TensorFlow, CoreML, MNN, NCNN, ExecuTorch, IMX, RKNN, Axelera, and DEEPX.

### 🧩 Export formats now declare their own environment

The internal `export_formats()` registry now includes environment metadata for every export target. This allows CI to understand exactly where each export should run, rather than relying on fragile manual logic.

### 🧪 New `--export-env` test selection

Tests can now be selected by export environment using `--export-env`, replacing older skip-based patterns with something much cleaner and less error-prone.

## Improvements

### ⚙ New `IsolatedExports` workflow

A new **`IsolatedExports`** CI job now creates dedicated virtual environments and runs smoke tests plus export tests inside them. This replaces the older shell-script-based coordination and makes the pipeline easier to reason about and extend.

### 📦 Leaner dependency groups

Export dependencies were split into smaller extras, helping keep installs more targeted and avoiding unnecessary heavy packages in base workflows.

Examples include:

- `export-base`
- `export-tensorflow`
- `export-coreml`
- `export-executorch`
- `export-deepx`
- `export-legacy-torch`

This should help both CI efficiency and local development workflows.

### 🌍 Better support for specialized deployment targets

This release improves validation paths for hardware-specific and edge deployment formats such as:

- IMX
- RKNN
- Axelera
- DEEPX
- ExecuTorch

That means stronger coverage for users deploying Ultralytics YOLO models beyond standard desktop or server environments.

## Bug Fixes and Reliability Enhancements

### ✅ Added checks for export registry consistency

New tests now verify that:

- every export environment has a smoke test
- every export format points to a valid registered environment

These checks help prevent registry mismatches and reduce maintenance mistakes as export support expands.

### 🤖 RKNN export test added

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

### 🐳 Docker cleanup improvements

Export Docker images now clean caches more aggressively, reducing leftover build artifacts and helping keep workflows tidier.

## Why this release matters

Even though `v8.4.58` is not a major end-user feature release, it has a meaningful impact for production and deployment workflows:

- 🔒 **More reliable exports** across formats
- 🚀 **Faster and leaner CI** for routine development
- 🧹 **Simpler maintenance** for export support going forward
- 📌 **Lower risk of one export backend breaking another**

In short: this release improves the foundation that powers model export across the ecosystem.

## Try it out

To upgrade locally:

```bash
pip install -U ultralytics

```

If you’re starting a new project, we recommend building with [Ultralytics YOLO26](https://platform.ultralytics.com/ultralytics/yolo26), our latest stable model family. You can also manage datasets, training, export, and deployment workflows through the [Ultralytics Platform](https://platform.ultralytics.com), which is the simplest way to annotate, train, and deploy YOLO models.

## PRs in this release

- [PR #24649: `ultralytics 8.4.58` Isolated CI export environments](https://github.com/ultralytics/ultralytics/pull/24649) by [@glenn-jocher](https://github.com/glenn-jocher)

## Feedback

Please give `v8.4.58` a try and let us know how it works for your export workflows 🙌  
If you spot any regressions, edge cases, or deployment-specific issues, we’d love your feedback from the community.