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 loginand delegatedul loginflows. - 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.
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 by @glenn-jocher
- Bump to v8.4.145 for login failure exit status — PR #26117 by @glenn-jocher
Try It Today
Upgrade from PyPI to receive the corrected login behavior:
pip install -U ultralytics==8.4.145
Review the complete release details in the Ultralytics v8.4.145 release, or explore every change in the full v8.4.144 to v8.4.145 changelog.
Please try the new release and share your feedback, especially if you use Platform authentication in CI or automated deployment workflows. ![]()