v0.2.0
March 13, 2026 Thev0.2.0 release expands the Device API from basic device health/version endpoints to deployment-pipeline visibility.
The current release version and current deployment endpoints are the most exciting, enabling on-device applications to verify that the release version of the config instances matches the application’s software version and programmatically inspect the deployment pipeline from the device itself.
New endpoints
Breaking changes
Additive changes
Python SDK
Beginning with thev0.2.0 Device API release, the Python SDK is published from python-device-sdk and uses the miru_device_sdk import path.
miru_agent_sdk import path.
Furthermore, SDK v0.3.0 marks the major version rollout of the v0.2.0 Device API. For the latest SDK version compatibility information, see the Device SDKs page.
Migration steps
Verify agent compatibility
Ensure all devices in your fleet are running Miru Agent v0.7.0 or later. See the agent compatibility matrix for details.
Migrate breaking changes
Migrate your client application according to the breaking changes listed above.If you are using the Python SDK, migrate from the legacy repository
python-agent-sdk to python-device-sdk. This migration includes updating imports from miru_agent_sdk to miru_device_sdk.v0.1.0
September 21, 2025 Initial release of the Device API. This version establishes the core on-device integration surface, including health checks, version metadata, device metadata, and a manual sync trigger.Endpoints
Python SDK
The initialv0.1.0 release used the legacy Python SDK repository python-agent-sdk and the miru_agent_sdk import path.
Current Device API Python SDK releases are published from python-device-sdk and use the miru_device_sdk import path.