# New Release: Ultralytics v8.4.145

**URL:** <https://community.ultralytics.com/t/new-release-ultralytics-v8-4-145/2209>\
**Category:** Discussion\
**Tags:** releases, announcements, ultralytics-official\
**Created:** [September 9, 2026, 1:09pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-4-145/2209 "2026-09-09T13:09:34Z")\
**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:** [September 9, 2026, 1:09pm UTC](https://community.ultralytics.com/t/new-release-ultralytics-v8-4-145/2209/1 "2026-09-09T13:09:34Z")

</div>

# 🚀 Ultralytics v8.4.145 Released

Ultralytics v8.4.145 improves **Platform login reliability** by ensuring authentication and connection failures return a non-zero exit status. This makes `yolo login` and `ul login` safer and more dependable in scripts, CI pipelines, and other automated workflows. ✅

## 🔐 Login Reliability Improvements

- Invalid API keys and rejected authentication requests now exit with **status 1**.
- Network and connection failures also return a failure status.
- The corrected behavior applies consistently to both `yolo login` and delegated `ul login` flows.
- Existing error messages remain available for clear troubleshooting.

## 🤖 Better Automation

Scripts and CI pipelines can now reliably detect failed login attempts instead of mistakenly treating them as successful.

```bash
yolo login YOUR_API_KEY
echo $?

```

A failed login now returns `1`, allowing automation to stop or handle the failure appropriately.

## 🛡 Safer Credential Handling

Failed login attempts do not overwrite valid saved credentials. Successful operations remain unchanged:

- Successful login saves credentials and exits normally.
- Logout clears credentials and returns status `0`.

## 🛠 Bug Fixes and Release Updates

- **Return failure status from Platform login** — [PR #26116](https://github.com/ultralytics/ultralytics/pull/26116) by [@glenn-jocher](https://github.com/glenn-jocher)
- **Bump to v8.4.145 for login failure exit status** — [PR #26117](https://github.com/ultralytics/ultralytics/pull/26117) by [@glenn-jocher](https://github.com/glenn-jocher)

## 📦 Try It Today

Upgrade from PyPI to receive the corrected login behavior:

```bash
pip install -U ultralytics==8.4.145

```

Review the complete release details in the [Ultralytics v8.4.145 release](https://github.com/ultralytics/ultralytics/releases/tag/v8.4.145), or explore every change in the [full v8.4.144 to v8.4.145 changelog](https://github.com/ultralytics/ultralytics/compare/v8.4.144...v8.4.145).

Please try the new release and share your feedback, especially if you use Platform authentication in CI or automated deployment workflows. 🙌