March Release

Scheduled for Mar 4, 09:00 - 09:30 CET

Scheduled

New Features
--------------

1. Commit API now accepts a list of changes directly in the request payload, committing them without needing the Change API. These changes are committed in isolation, meaning any existing uncommitted changes will not be included. This improves workflows where parallel processes need to commit configuration changes independently.

2. Updated the look and feel of the REST API documentation.

3. Improved tracking of expected releases—the inventory API now returns a new property, config_status, with one of three values:

- queued – the device hasn't received the new config yet.
- processing – the device has received the config but hasn't applied it yet.
- applied – the device has successfully applied the current config.

The expected configuration commit ID will change when any of the following occur:

- Configuration changes (on the device, its ancestors, or tags).
- Device tree structure changes (tags changed, device moved to another group).
- File changes (for files referenced by the current device configuration).


Fixes
-----

1. Resolved a file streaming issue during RAUC updates for accounts created in February 2026 and those using Bring-Your-Own-CA.


Maintenance
-------------

1. Performed regular system patching and infrastructure updates.
Posted Mar 03, 2026 - 08:47 CET
This scheduled maintenance affects: Platform Status (Frontend, Device Hub, Remote Access).