New Release: Ultralytics v8.3.209

Ultralytics v8.3.209 — Reliable RT‑DETR → TensorFlow/TFLite exports, tuner fix, and docs/CI updates :rocket:

Summary
Ultralytics v8.3.209 focuses on export reliability and tooling polish. RT-DETR exports to TensorFlow/TFLite are now robust by automatically enforcing ONNX opset 19, hyperparameter tuning gets a correctness fix when resuming, and we’ve refreshed CI and documentation assets. YOLO11 and YOLO26 models and other export paths are unaffected by these changes.

New Features

  • No new features this cycle—this release concentrates on reliability and developer experience improvements.

Improvements

Bug Fixes

Purpose & Impact

  • Stronger export reliability for RT-DETR: enforcing ONNX opset 19 avoids the conversion failures many saw with higher opsets and can override a user-provided higher opset to ensure success.
  • Smoother export experience: newer onnxslim improves ONNX graph simplification, reducing export friction.
  • More accurate experiments: the tuner fix prevents incorrect “best run” selection when resuming.
  • Clearer docs and steadier CI: improved branding and centralized CI visibility, with a temporary GPU CI pause to stabilize pipelines.

Quick Start

  • Export RT-DETR to TensorFlow or TFLite from the CLI:
    • yolo export model=rtdetr.pt format=tf
    • yolo export model=rtdetr.pt format=tflite
  • Export from Python:
    from ultralytics import YOLO
    
    model = YOLO("rtdetr.pt")
    model.export(format="tf")      # TensorFlow SavedModel
    model.export(format="tflite")  # TFLite
    
  • If you’re new to RT-DETR, you can skim the RT-DETR model docs for task support and usage notes. For most new projects we recommend starting with YOLO11; this release does not alter YOLO11 or the in‑progress YOLO26 R&D line.

What’s Changed (PRs and Authors)

Get the Release

Try It and Share Feedback

  • Upgrade with pip install -U ultralytics, try the improved exports, and let us know how it goes. We welcome your thoughts in GitHub Discussions and issues, and we appreciate reproducible examples if you encounter any edge cases. Your feedback helps the whole YOLO community move forward.