🔨 Fixed

Incompatibility of opencv-python with numpy>=2.0.0 ⚔️

Jun 16, there was release of numpy 2.0 making old builds of opencv-python incompatible with new numpy.

@grzegorz-roboflow investigated the issue and discovered that inference users can be impacted if package inference-sdk was used standalone, due to lack of upper-bound limit on numpy dependency in that library.

To support impacted community members and Roboflow clients, we've prepared release with bug-fix.

Symptoms of the problem:

A module that was compiled using NumPy 1.x cannot be run in
NumPy 2.0.0 as it may crash. To support both 1.x and 2.x
versions of NumPy, modules must be compiled with NumPy 2.0.
Some module may need to rebuild instead [...]

If you are a user of the module, the easiest solution will be to
downgrade to 'numpy<2' or try to upgrade the affected module.
We expect that some modules will need time to support NumPy 2.

To solve the problem choose one of the following solutions:

pip install "inference>=0.12.1"
# or 
pip install "inference-cli>=0.12.1"
# or 
pip install "inference-sdk>=0.12.1"

# in your Python environment hosting inference library
pip install "numpy<2.0.0"

We are sorry for inconvenience.

❗ Planned deprecations

• np_image_to_base64(...) to be replaced with encode_image_to_jpeg_bytes(...) in the future - @grzegorz-roboflow in #469

🌱 Changed

• Remove sv.FPSMonitor deprecation warnings by @grzegorz-roboflow in #461
• Loose boto3 requirements by @iurisilvio in #457 - inference should install faster now 🤗
• Fix paligemma generation bug by @probicheaux in #459
• Add support for a tunnel to expose inference server to remote calls by @iurisilvio in #451
• Workflow documentation additions, add YOLOv10 docs by @capjamesg in #475
• fix Docker Getting Started link in docs returns 404 by @grzegorz-roboflow in #478

🏅 New Contributors

• @iurisilvio made their first contribution in #457

Full Changelog: v0.12.0...v0.12.1