v0.59.0

💪 Added

🍾 Workflows Execution Engine v1.7.0

This release refines how Workflow step errors are reported when interacting with the Roboflow platform. Client-side issues such as invalid API keys or model IDs now raise ClientCausedStepExecutionError with accurate HTTP status codes (400–404) instead of a generic StepExecutionError with HTTP 500.

Motivation

The change ensures that client misconfigurations are clearly distinguished from server-side errors, improving observability and making debugging easier.

Compatibility

Most users should not be affected. However, if an integration relies on the legacy error type or status code, it can be temporarily restored by setting:

DEFAULT_WORKFLOWS_STEP_ERROR_HANDLER=legacy

This update brings more accurate error reporting with minimal impact on existing workflows. See details of the change in the Workflows change log and in PR #1640

🥼 Changes inference-experimental

• Add changes to inference-exp deeplab sem-seg model by @PawelPeczek-Roboflow in #1629
• Adjust the name of yolov5 weights by @PawelPeczek-Roboflow in #1633
• Add tests for Yolov7 implementation by @PawelPeczek-Roboflow in #1634
• Add ability for inference-exp to parse modelVariant from RFAPI by @PawelPeczek-Roboflow in #1641
• Add PaliGemma 1 to inference-exp by @PawelPeczek-Roboflow in #1639
• YOLACT in inference experimental by @PawelPeczek-Roboflow in #1637
• Adjust YOLACT tests assertions for GPU tests to pass by @PawelPeczek-Roboflow in #1638

Full Changelog: v0.58.3...v0.59.0