2026-11-04.everglades
November 4, 2026 Thiseverglades update records who did what. Resources now report the principal that created them, archivable resources report when they were archived and by whom, and deployments report who staged and queued them. It also adds read access to workspace members and API keys, and lets API keys archive, unarchive and delete releases.
Every change is additive. 2026-10-29.everglades and 2026-08-17.everglades remain supported Miru-Version values, so existing integrations keep working without changes.
New endpoints
Users and API keys have their ownread scopes, and deleting a release needs the new releases:delete scope.
Additive changes
Migration steps
Update the Miru-Version header
Miru-Version: 2026-11-04.everglades on API requests. Requests that send 2026-10-29.everglades or 2026-08-17.everglades keep working. Python SDK v0.14.0 marks the rollout of the 2026-11-04.everglades API. For the latest SDK version compatibility information, visit the Platform SDKs page.Review release scopes
releases:write can now archive and unarchive releases, and API keys with releases:manage can now delete them. Narrow those keys’ scopes if they shouldn’t.Optionally integrate new endpoints
releases:delete, users:read or api_keys:read scopes they need.Optionally adopt new additive surface
2026-10-29.everglades
October 29, 2026 Thiseverglades update adds read access to calibrations. Devices report calibrations starting with Miru Agent v0.12.0. Devices now report the operating system, CPU architecture, hostname, and kernel they run, and releases gain a free-form description.
Every change is additive. 2026-08-17.everglades remains a supported Miru-Version value, so existing integrations keep working without changes.
New endpoints
Calibrations have their ownread and manage scopes.
Additive changes
Migration steps
Update the Miru-Version header
Miru-Version: 2026-10-29.everglades on API requests. Requests that send 2026-08-17.everglades keep working. Python SDK v0.13.0 marks the rollout of the 2026-10-29.everglades API. For the latest SDK version compatibility information, visit the Platform SDKs page.Handle the csv instance format
instance_format or config instance content format, handle the new csv value.Optionally integrate new endpoints
Optionally adopt new additive surface
2026-08-17.everglades
August 17, 2026 Theeverglades release introduces device groups, allowing you to build your fleet hierarchy via API and access device group information. Groups themselves are fully manageable: create, rename, and move them as desired. A device’s membership in a group is read-only, so assigning a device to a group remains a dashboard flow.
everglades also brings the Platform API up to date with three months of configuration changes: config schemas now support instance slots, deployments report more timestamps (queued, deployed, archived), and devices report an archived status.
New endpoints
Breaking changes
Additive changes
Migration steps
Update the Miru-Version header
Miru-Version: 2026-08-17.everglades on all API requests. Python SDK v0.11.0 marks the major version rollout of the 2026-08-17.everglades API. For the latest SDK version compatibility information, visit the Platform SDKs page.Migrate from config schemas to use instance slots
instance_filepath with instance_slots[].filepath, and replace instance_filepath in POST /config_schemas request bodies with an explicit instance_slots array. Omitting instance_slots makes the server derive a default filepath rather than reuse your previous one. See instance slots.Stop sending slug when updating a config type
slug from PATCH /config_types/{config_type_id} request bodies. Config type slugs are immutable.Review parent_id when creating deployments
parent_id or always send a deployment ID. Send null only to assert that the device has no current target deployment.Optionally integrate new endpoints
Optionally adopt new additive surface
2026-05-06.rainier
May 12, 2026 Therainier release introduces a provisioning-token flow that replaces the activation-token endpoint, expands supported config-instance content formats, restores the removing deployment status, and adds expandable current_release / current_deployment fields on devices.
New endpoints
Breaking changes
Additive changes
Migration steps
Update the Miru-Version header
Miru-Version: 2026-05-06.rainier on all API requests. Python SDK v0.10.0 marks the major version rollout of the 2026-05-06.rainier API. For the latest SDK version compatibility information, visit the Platform SDKs page.Migrate from activation tokens to provisioning tokens
Optionally adopt new additive surface
- Handle
yamlcontent format where needed - Handle
removingdeployment status or activity status where needed. - Implement or migrate to
expand=current_releaseand/orexpand=current_deploymentfor retrieving the current release or deployment on a device.
2026-03-09.tetons
March 13, 2026 Thetetons release introduces API versioning and overhauls the representation of deployments, config instances, and config schemas. It introduces management of more configuration resources (config types, schemas, and instances), release creation, git commit tracking, and explicit deployment lifecycle actions.
New endpoints
Breaking changes
Additive changes
Python SDK
Beginning with the2026-03-09.tetons release, the Python SDK is published from python-platform-sdk and uses the miru_platform_sdk import path.
miru_server_sdk import path.
Furthermore, SDK v0.7.0 marks the major version rollout of the 2026-03-09.tetons API. For the latest SDK version compatibility information, see the Platform SDKs page.
Migration steps
Set the Miru-Version header
Miru-Version: 2026-03-09.tetons header on all API requests. If you are using the Python SDK, this is done automatically.Migrate breaking changes
miru_server_sdk to miru_platform_sdk.Optionally integrate new endpoints
2025-10-21.zion
October 21, 20252025-10-21.zion API version is no longer supported. See supported versions.Endpoints
Query parameters
Python SDK
2025-10-21.zion comes with an official Python SDK published to python-server-sdk. For more details on usage, visit the python-server-sdk repository.

