๐ Summary
v8.4.98 improves Hailo export compatibility for legacy YOLO checkpoints while preserving strict model-family validation. ๐
๐ Key Changes
-
Legacy checkpoint support for Hailo export ๐ ๏ธ
Hailo exports can now identify the model family from its architecture when older checkpoints do not include the optionalyaml_filemetadata. -
Topology-based model detection ๐
The exporter examines backbone and head components to recognize supported YOLOv8, YOLO11, and YOLO26 checkpoints when metadata is missing. -
Existing validation remains intact โ
The detection-head checks and supported-family restrictions were preserved, preventing unsupported architectures such as YOLOv5, YOLOv10, and YOLO12 from being sent to Hailoโs Dataflow Compiler. -
Patch version updated ๐ฆ
The package version was incremented from8.4.97to8.4.98.
๐ฏ Purpose & Impact
- More reliable deployment of older models: Legacy trained checkpoints can now be exported to Hailo without requiring metadata that was not consistently stored in older versions.
- No change to supported model scope: The update improves checkpoint recognition rather than adding unsupported model families.
- Safer exports: Existing architecture validation continues to catch incompatible models before Hailo compilation, reducing confusing downstream failures.
- Broad compatibility coverage: Testing confirmed that metadata-stripped YOLOv8, YOLO11, and YOLO26 checkpoints are accepted, while unsupported families are correctly rejected. ๐งช
What's Changed
- Support legacy checkpoints in Hailo export by @glenn-jocher in #25237
Full Changelog: v8.4.97...v8.4.98