# New Release: Ultralytics v8.4.115

**URL:** <https://community.ultralytics.com/t/new-release-ultralytics-v8-4-115/2151>\
**Category:** Discussion\
**Tags:** releases, announcements, ultralytics-official\
**Created:** [August 2, 2026, 1:31pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-4-115/2151 "2026-08-02T13:31:07Z")\
**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:** [August 2, 2026, 1:31pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-4-115/2151/1 "2026-08-02T13:31:08Z")

</div>

# 🚀 Ultralytics v8.4.115: A Streamlined Platform Experience

Ultralytics **v8.4.115** transitions legacy HUB integrations to the streamlined [Ultralytics Platform](https://platform.ultralytics.com/) experience, introducing validated CLI authentication, safer settings migration, cleaner training workflows, updated documentation, and expanded tests.

## 🌟 New Features

### 🔐 Validated Platform CLI authentication

Authentication is now simpler and more secure. Log in using a Platform API key:

```bash
yolo login YOUR_API_KEY

```

API keys are validated against the Platform before being saved. To remove stored credentials, run:

```bash
yolo logout

```

### 🔄 Automatic settings migration

Settings now migrate to schema `0.0.7` during upgrades:

- Compatible custom dataset and run directories are preserved.
- Legacy HUB configuration is removed automatically.
- Incompatible HUB API keys are discarded.
- Users with outdated credentials are guided toward creating a Platform API key.

## ⚡ Improvements

### 🧠 Leaner model and training workflows

This release removes legacy HUB session management from model and trainer workflows:

- Models no longer load directly from HUB URLs.
- Training no longer manages HUB sessions, remote checkpoints, heartbeats, or HUB-specific arguments.
- Platform callbacks remain available for streaming training information.

These changes reduce integration complexity and make the training codebase easier to maintain.

### 📚 Updated documentation and examples

Guides, notebooks, CLI help, quickstarts, and API documentation now reference the Ultralytics Platform instead of HUB. The updated experience makes it easier to annotate datasets, train models, export deployments, and monitor results in one place.

## 🧹 Legacy HUB Removal

The legacy `ultralytics.hub` package has been removed, including:

- HUB authentication and remote training sessions
- HUB model loading and exports
- Dataset utilities and callbacks
- HUB-specific exceptions
- Related API references, documentation pages, navigation entries, and example notebooks

> ⚠ **Compatibility note:** Applications importing `ultralytics.hub`, loading models from HUB URLs, using HUB training sessions, or relying on HUB-specific utilities must migrate to Ultralytics Platform workflows.

## ✅ Testing and Reliability

Test coverage has been expanded for:

- Settings migration
- API-key validation
- CLI login behavior
- CLI logout behavior

This helps ensure safer upgrades while preserving compatible user configuration.

## 🙌 Contributor Spotlight

This release was delivered through [PR #25608: Deprecate HUB in favor of Ultralytics Platform](https://github.com/ultralytics/ultralytics/pull/25608), contributed by [@sergiuwaxmann](https://github.com/sergiuwaxmann). Thank you for helping simplify and modernize the Ultralytics experience! 🎉

## 📦 Try v8.4.115

Upgrade to the latest release:

```bash
pip install -U ultralytics

```

Then create a Platform API key and authenticate:

```bash
yolo login YOUR_API_KEY

```

You can review the complete changes in the [v8.4.114 to v8.4.115 changelog](https://github.com/ultralytics/ultralytics/compare/v8.4.114...v8.4.115) or visit the [Ultralytics v8.4.115 release page](https://github.com/ultralytics/ultralytics/releases/tag/v8.4.115) for release details.

Give v8.4.115 a try and share your feedback, migration experience, or any issues you encounter with the community. 🚀