# New Release: Ultralytics v8.3.249

**URL:** <https://community.ultralytics.com/t/new-release-ultralytics-v8-3-249/1730>\
**Category:** Discussion\
**Tags:** releases, announcements, ultralytics-official\
**Created:** [January 7, 2026, 1:16pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-3-249/1730 "2026-01-07T13:16:59Z")\
**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:** [January 7, 2026, 1:16pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-3-249/1730/1 "2026-01-07T13:16:59Z")

</div>

# 🚀 Ultralytics v8.3.249 is out! 🐳⚡ (YOLO11 on NVIDIA ARM64 / JetPack 7)

**TL;DR:** Ultralytics **v8.3.249** ships an official **NVIDIA ARM64 Docker image** for running **Ultralytics YOLO (YOLO11)** on **JetPack 7 / ARM64 GPUs** , plus `ul://` URI support, a small analytics overlay fix, and contributor/docs improvements. ✅

* * *

## 🐳 New Feature: Official NVIDIA ARM64 Docker image (JetPack 7 / ARM64 GPUs)

If you’re deploying on **Jetson AGX Thor** , **DGX Spark** , or other **JetPack 7** ARM64 platforms, this release adds a first-class container path:

- Added `docker/Dockerfile-nvidia-arm64` based on NVIDIA PyTorch NGC (`nvcr.io/nvidia/pytorch:25.10-py3`)
- CI now builds & publishes **`ultralytics/ultralytics:latest-nvidia-arm64`**
- Container “it just works” improvements:
  - Uses `opencv-python-headless` to avoid GUI dependency issues in containers 🧩
  - Installs ARM64 `onnxruntime_gpu` and reinstalls `torch/torchvision` for CUDA compatibility 🔥
  - Preloads Ultralytics fonts and includes a default YOLO11 model (`yolo11n.pt`) 📦

- JetPack 7 docs updated with pull/run commands ✅

Try it:

```bash
t=ultralytics/ultralytics:latest-nvidia-arm64
sudo docker pull $t && sudo docker run -it --ipc=host --runtime=nvidia $t

```

* * *

## 🔗 New Feature: `ul://` URI support (Platform-style referencing)

You can now reference assets via `ul://...` and let Ultralytics handle secure resolution + download:

- New `resolve_platform_uri()` resolves `ul://...` to signed download URLs (via `ULTRALYTICS_API_KEY`)
- `check_file()` now accepts `ul://...` and auto downloads/caches locally 📥🗂
- Clearer errors for invalid keys, forbidden access, not found, and “still processing” cases 🚦

* * *

## 🛠 Bug Fix: ObjectCounter label display logic

A small but important fix to analytics overlays:

- Corrected operator precedence in `ObjectCounter.display_counts` so `show_in` / `show_out` behave properly (prevents empty/incorrect labels)

* * *

## 📝 Contributor / Docs Improvements

Contributor workflow got clearer and more streamlined:

- Updated `CONTRIBUTING.md` with PR size/scope guidance, feature PR expectations, and automated review notes 🤝

* * *

## ✅ What’s Changed (PRs)

- Add scope and PR size guidelines to `CONTRIBUTING.md` by [@Y-T-G](https://github.com/Y-T-G) in [PR #23133](https://github.com/ultralytics/ultralytics/pull/23133)
- Fix typo in CONTRIBUTING.md guidelines by [@Y-T-G](https://github.com/Y-T-G) in [PR #23134](https://github.com/ultralytics/ultralytics/pull/23134)
- Fix operator precedence in `ObjectCounter.display_counts` by [@raimbekovm](https://github.com/raimbekovm) in [PR #23132](https://github.com/ultralytics/ultralytics/pull/23132)
- URI resolution by [@glenn-jocher](https://github.com/glenn-jocher) in [PR #23136](https://github.com/ultralytics/ultralytics/pull/23136)
- `ultralytics 8.3.249` Jetson AGX Thor and DGX Spark Docker by [@lakshanthad](https://github.com/lakshanthad) in [PR #23111](https://github.com/ultralytics/ultralytics/pull/23111)

* * *

## 🔄 Upgrade & Share Feedback

Upgrade with:

`pip install -U ultralytics`

You can review the full details in the [v8.3.249 GitHub release](https://github.com/ultralytics/ultralytics/releases/tag/v8.3.249), and browse the [full changelog comparing v8.3.248…v8.3.249](https://github.com/ultralytics/ultralytics/compare/v8.3.248...v8.3.249).

If you try the new ARM64 container (or the new `ul://` flows), let us know what hardware you’re running and how it goes—feedback helps us keep edge deployments smooth and reproducible.