# New Release: Ultralytics v8.4.82 **URL:** \ **Category:** Discussion\ **Tags:** releases, announcements, ultralytics-official\ **Created:** [June 29, 2026, 2:24pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-4-82/2088 "2026-06-29T14:24:22Z")\ **Posts on this page:** 1\ **Page:** 1
**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:** [June 29, 2026, 2:24pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-4-82/2088/1 "2026-06-29T14:24:22Z")
# Ultralytics v8.4.82 is out 🚀 **Quick summary:** Ultralytics v8.4.82 is a stability-focused release that makes **Ultralytics YOLO** workflows more reliable, especially for **YOLO26 Axelera exports** , classification RAM caching, and training/data edge cases. If you’re deploying YOLO26 or training classification models at scale, this update is worth grabbing. ✅ You can explore the release on [GitHub Releases](https://github.com/ultralytics/ultralytics/releases/tag/v8.4.82) and review the [full changelog](https://github.com/ultralytics/ultralytics/compare/v8.4.81...v8.4.82). ## 🌟 Highlights ### 🚀 More reliable YOLO26 Axelera exports This is the biggest fix in v8.4.82. We fixed an issue where Axelera export could accidentally remove its own generated files when run from the model directory, leading to confusing failures like “output model too small” even when compilation had actually succeeded. This release: - Uses a safer temporary compile directory - Prevents cleanup from deleting valid outputs - Adds better export serialization to avoid shared-state conflicts - Restores support for `end2end=False` exports where supported This should make deployment pipelines much more dependable, including automated jobs on the [Ultralytics Platform](https://platform.ultralytics.com). ### 🧠 Classification `cache='ram'` is back, safely Classification training can now use `cache='ram'` again without the previous memory growth issue. Instead of duplicating decoded images across workers, images are now stored in a **shared memory buffer** , improving memory efficiency while preserving the speed benefits of RAM caching. ### 🛑 Faster failure for empty-label datasets Training now stops immediately with a clear error when a detection dataset contains no usable labels at all. This helps catch dataset issues earlier and avoids more confusing failures later in training. ### 🖼 Better real-world image handling We improved image format handling by: - Adding proper fallback support for `.heif` - Removing the invalid `.jpeg2000` extension from supported image lists ### 🧹 Python reliability improvements Several subtle mutable default argument bugs were fixed across metrics, TAL, augmentations, YOLOE, and SAM-related code. These changes improve long-running reliability in notebooks, services, and repeated train/infer workflows. ## Improvements ### 📚 Docs and workflow polish A few helpful quality-of-life updates landed as well: - Clearer documentation for `stream=True` behavior in predict mode - Added docs for `MLFLOW_KEEP_RUN_ACTIVE` for MLflow users - Updated citations for YOLOv7, YOLOv9, YOLOv10, and YOLO12 docs - Cleaner Slack release and CI notifications ## What’s changed - [Guard YOLO26 Axelera end2end exports](https://github.com/ultralytics/ultralytics/pull/24962) by [@glenn-jocher](https://github.com/glenn-jocher) - [Restore Axelera `end2end=false` exports](https://github.com/ultralytics/ultralytics/pull/24963) by [@glenn-jocher](https://github.com/glenn-jocher) - [Fix mutable default args in metrics and TAL](https://github.com/ultralytics/ultralytics/pull/24631) by [@raimbekovm](https://github.com/raimbekovm) - [Fix mutable default args in augment, YOLOE, and SAM](https://github.com/ultralytics/ultralytics/pull/24630) by [@raimbekovm](https://github.com/raimbekovm) - [Restore fail-fast when training labels are all empty](https://github.com/ultralytics/ultralytics/pull/24562) by [@AffanBinFaisal](https://github.com/AffanBinFaisal) - [Document `MLFLOW_KEEP_RUN_ACTIVE` for MLflow integration](https://github.com/ultralytics/ultralytics/pull/24602) by [@raimbekovm](https://github.com/raimbekovm) - [Update YOLOv7, YOLOv9, YOLOv10, and YOLO12 citations](https://github.com/ultralytics/ultralytics/pull/24501) by [@banu4prasad](https://github.com/banu4prasad) - [Clarify `stream=True` behavior](https://github.com/ultralytics/ultralytics/pull/24657) by [@seungcle](https://github.com/seungcle) - [Drop phantom `jpeg2000` extension and fix `heif` loader fallback](https://github.com/ultralytics/ultralytics/pull/24594) by [@raimbekovm](https://github.com/raimbekovm) - [Refactor comments in `tests/ __init__.py` for clarity](https://github.com/ultralytics/ultralytics/pull/24651) by [@penampungdipek-creator](https://github.com/penampungdipek-creator) - [Fix classification `cache='ram'` leak via shared memory tensor](https://github.com/ultralytics/ultralytics/pull/24670) by [@raimbekovm](https://github.com/raimbekovm) - [Simplify Slack notification messages](https://github.com/ultralytics/ultralytics/pull/24964) by [@glenn-jocher](https://github.com/glenn-jocher) - [Fix Axelera export deleting its output when run from the model directory](https://github.com/ultralytics/ultralytics/pull/24965) by [@glenn-jocher](https://github.com/glenn-jocher) ## 🙌 New contributors Thanks to our new contributors for jumping in: - [@seungcle](https://github.com/seungcle) for their first contribution in [PR #24657](https://github.com/ultralytics/ultralytics/pull/24657) - [@penampungdipek-creator](https://github.com/penampungdipek-creator) for their first contribution in [PR #24651](https://github.com/ultralytics/ultralytics/pull/24651) ## Try it out Update with: ```bash pip install -U ultralytics ``` If you’re starting a new project, we recommend [YOLO26 on Ultralytics Platform](https://platform.ultralytics.com/ultralytics/yolo26) for the latest and best-performing Ultralytics model family, with full support for detect, segment, classify, pose, and OBB workflows. ## Feedback welcome 💬 Please give v8.4.82 a try and let us know how it works in your training and deployment pipelines. Feedback, bug reports, and regression checks are always appreciated from the community.