# New Release: Ultralytics v8.3.234

**URL:** <https://community.ultralytics.com/t/new-release-ultralytics-v8-3-234/1682>\
**Category:** Discussion\
**Tags:** releases, announcements, ultralytics-official\
**Created:** [December 2, 2025, 1:16pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-3-234/1682 "2025-12-02T13:16:18Z")\
**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:** [December 2, 2025, 1:16pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-3-234/1682/1 "2025-12-02T13:16:18Z")

</div>

# 🚀 Ultralytics v8.3.234 Release – Safer, Smoother, More Robust

Ultralytics `v8.3.234` is a focused maintenance release that improves **model metadata safety** , **Albumentations training robustness** , and the **docs & tooling experience**. No breaking changes and fully safe to drop into existing YOLO workflows. ✅

If you are using YOLO11 or other Ultralytics YOLO models today, you can upgrade confidently and benefit from better security, stability, and documentation UX.

* * *

## 🌟 Summary

- 🔐 Safer handling of model metadata in exports using `ast.literal_eval`
- 🧪 More robust Albumentations label shapes for training pipelines
- 🐍 Cleaner dev experience with Python 3.10+ alignment
- 🎥 New segmentation video tutorial for object isolation
- 🤖 Upgraded in-docs LLM assistant for a smoother docs experience
- ✨ JavaScript and CSS cleanups improving docs UI maintainability

You can review the full release entry in the Ultralytics GitHub [v8.3.234 release notes](https://github.com/ultralytics/ultralytics/releases/tag/v8.3.234).

* * *

## 🆕 New & Notable

### 🔐 Safer model metadata parsing

Model export paths now use **`ast.literal_eval`** instead of `eval` when parsing string metadata such as `imgsz`, `names`, `kpt_shape`, `kpt_names`, and `args` in `torch_to_mnn` inside the autobackend. This greatly reduces the risk of executing arbitrary code from crafted metadata in exported models.

- Implemented in [Security fix: `ast.literal_eval` for safer evaluation of metadata strings](https://github.com/ultralytics/ultralytics/pull/22847) by [@onuralpszr](https://github.com/onuralpszr)

A few remaining `eval` calls in `cfg2task` are now explicitly marked with `# nosec B307` to document that they are controlled and safe for known attributes.

* * *

### 🧪 More robust Albumentations label handling

Albumentations-based pipelines can now rely on consistent label shapes:

- `labels["cls"]` is always reshaped to a **2D column array** `(num_boxes, 1)`
- This prevents subtle shape mismatch issues during training when chaining transforms

Implemented in [fix: reshape class labels in Albumentations transform](https://github.com/ultralytics/ultralytics/pull/22846) by [@onuralpszr](https://github.com/onuralpszr).

* * *

## 📚 Docs, Tutorials & UI Enhancements

### 🎥 New segmentation video tutorial

The **object isolation with segmentation** guide now includes a step‑by‑step YouTube tutorial showing how to:

- Use **Ultralytics YOLO segmentation + OpenCV in Python**
- Remove backgrounds and isolate objects from images

Added in [Add segmentation video tutorial to docs](https://github.com/ultralytics/ultralytics/pull/22825) by [@RizwanMunawar](https://github.com/RizwanMunawar).

A minimal example for segmentation-based object isolation might look like:

```python
from ultralytics import YOLO
import cv2

model = YOLO("yolo11n-seg.pt") # example segmentation model
results = model("image.jpg")

for r in results:
    for mask in r.masks.data:
        # Convert mask tensor to uint8 image
        m = (mask.cpu().numpy() * 255).astype("uint8")
        # Apply mask to original image as needed

```

* * *

### 🤖 Upgraded in-docs LLM chat widget

The embedded Ultralytics chat widget used in the docs has been upgraded through several versions to improve:

- Stability and responsiveness
- Feature set for in‑browser assistance

This was done across:

- [Update to v0.0.9/js/chat.min.js](https://github.com/ultralytics/ultralytics/pull/22832) by [@glenn-jocher](https://github.com/glenn-jocher)
- [Update to chat.js v0.1.0](https://github.com/ultralytics/ultralytics/pull/22845) by [@glenn-jocher](https://github.com/glenn-jocher)
- [Update to @v0.1.2/js/chat.min.js](https://github.com/ultralytics/ultralytics/pull/22861) by [@glenn-jocher](https://github.com/glenn-jocher)

No user‑side configuration changes are required; you will simply get a better helper when browsing docs.

* * *

### ✨ JavaScript & CSS cleanups

Docs UI scripts and styles received a round of cleanup to improve maintainability and reduce subtle bugs:

- Modernized JavaScript with arrow functions, template literals, `Number.parseInt`, `Number.parseFloat`, and `Number.isNaN`
- Cleaned CSS by removing excessive `!important` and clarifying key UI components

These changes landed in:

- [Biome format](https://github.com/ultralytics/ultralytics/pull/22842) by [@pderrenger](https://github.com/pderrenger)
- [Biome fixes](https://github.com/ultralytics/ultralytics/pull/22844) by [@pderrenger](https://github.com/pderrenger)

* * *

### 🔗 Documentation & link updates

A few docs have been updated to provide more reliable commands and accurate external links:

- Jetson deployment guide now pulls the `onnxruntime-gpu` wheel directly from a **Ultralytics GitHub asset** , simplifying copy‑paste and avoiding outdated links, as part of [Change `onnxruntime-gpu` download from Ultralytics assets](https://github.com/ultralytics/ultralytics/pull/22823) by [@lakshanthad](https://github.com/lakshanthad)
- Axelera integration docs now link to the correct Ultralytics blog posts for **YOLO11 drone** and **traffic/ANPR** use cases in [Fix links in docs](https://github.com/ultralytics/ultralytics/pull/22829) by [@glenn-jocher](https://github.com/glenn-jocher)

* * *

## 👨‍💻 Developer Experience & Tooling

### 🐍 Python 3.10+ alignment for dev installs

The `zensical` dev dependency now explicitly requires **Python 3.10 or higher** , aligning with what the docs tooling already expects. This helps avoid confusing dependency resolution errors when you work on Ultralytics in dev mode.

- Implemented in [fix: update zensical dependency to require Python 3.10 or higher](https://github.com/ultralytics/ultralytics/pull/22830) by [@onuralpszr](https://github.com/onuralpszr)

If you contribute to Ultralytics or develop locally, a typical setup remains:

```bash
pip install -e ".[dev]"

```

Just ensure you are on Python 3.10+.

* * *

## 🔢 Version Bump

The library version was updated from `8.3.233` to **`8.3.234`** , captured in:

- [ultralytics 8.3.234 security and maintenance update](https://github.com/ultralytics/ultralytics/pull/22847) by [@onuralpszr](https://github.com/onuralpszr)

You can compare all changes in the full diff using the GitHub [v8.3.233 → v8.3.234 comparison view](https://github.com/ultralytics/ultralytics/compare/v8.3.233...v8.3.234).

* * *

## 🎯 Why Upgrade?

- 🛡 **Stronger safety** when loading and exporting models, especially if you work with external or untrusted weights
- ⚙ **More stable training** when using Albumentations-heavy pipelines
- 👨‍💻 **Clearer dev environment requirements** and smoother contributor experience
- 📚 **Better learning resources** , particularly around segmentation and deployment on edge hardware
- 🤖 **Improved docs assistant** , giving you a more helpful in-browser companion

All of this comes **without** changing your existing YOLO training or inference code.

* * *

## ✅ How to Try It

Upgrade to the latest Ultralytics release:

```bash
pip install -U ultralytics

```

Then run a quick check with your usual command, for example:

```bash
yolo detect predict model=yolo11n.pt source=path/to/images

```

or for segmentation:

```bash
yolo segment predict model=yolo11n-seg.pt source=path/to/images

```

* * *

## 💬 Feedback & Discussion

The Ultralytics team and community would love to hear how `v8.3.234` works for you:

- Did the safer metadata parsing help with any exported models?
- Are Albumentations pipelines running smoother?
- Any suggestions for the docs, tutorials, or tooling?

Please share your thoughts, questions, or issues in this thread or open an issue or discussion in the Ultralytics GitHub repository. Your feedback directly shapes future YOLO and Ultralytics releases. 🙏