Changelog
Version history and release notes for ModularIoT.
Version Format
We follow semantic versioning: MAJOR.MINOR.PATCH
- MAJOR - Breaking changes
- MINOR - New features, backward compatible
- PATCH - Bug fixes, backward compatible
Upcoming
Features and improvements in development:
- JavaScript, Python, and Java SDKs
- Advanced symptom patterns
- Enhanced notification channels
- Historical analytics dashboard
Recent Releases
Dashboard server v0.8.0 (2026-10-15)
Published the server v0.8.0:
MIOT_DASHBOARD_TICKET_ALLOW_HTTP=trueaccepts a plainhttp://ticket validation URL, for an issuer on the same private network. Before, only https or loopback was accepted. Requires contract^0.6.0.
Dashboard UI v0.1.2 (2026-10-08)
Published the dashboard UI v0.1.2:
- A widget dragged in edit mode stays under the pointer. Before, the first move threw it away by the grid’s distance from the page corner, such as a sidebar and header.
Dashboard UI v0.1.1 (2026-10-07)
Published the dashboard UI v0.1.1:
- In edit mode, a widget can be dragged from anywhere on it, including the middle of a table or a chart. While the grid can drag, a widget’s content no longer scrolls, takes the pointer or selects text. Controls in the host’s
Frameand container widgets stay interactive.
Dashboard server v0.7.0 (2026-10-06)
Published the server v0.7.0:
MIOT_DASHBOARD_GROUP_ROLES_PATTERNandMIOT_DASHBOARD_GROUP_ROLES_MAPread organization and scope roles from the caller’s groups, such asGROUP_DHB_{tenant}_{role}, with no seed file or lookup service (guide).createGroupRoleAuthoritiesdoes the same for library users. Requires contract^0.6.0.
Dashboard packages v0.6.0 and dashboard UI v0.1.0 (2026-10-05)
Published contract and server v0.6.0, and the first release of the dashboard UI , v0.1.0:
- Contract v0.6.0: filters can declare
singleselection and take their options from a saved query result (optionsSource). The OpenAPI document adds the query catalog route, and list summaries carry the dashboard’sorder. - Server v0.6.0: an optional query catalog provider lists approved connections, operations and result columns to editors, without credentials.
createRemoteQueryCatalogreads it from a host endpoint. Lists are sorted byorder.plannerOperationContractsandmigratePlannerQueriesconvert request-planner dashboards to saved queries (guide). Requires contract^0.6.0. - UI v0.1.0, first release: React, Web Component and plain-browser rendering of the dashboard catalog, and authoring for settings, saved queries, permissions, filters and import/export.
useDashboardAutosavesaves a document once edits pause. Requires contract^0.6.0; React 18 or 19 and ECharts 6 are peer dependencies.
Dashboard packages v0.5.0 — Creation permissions (2026-09-29)
Published compatible contract and server v0.5.0:
- New scope capabilities endpoint and embedded method let a workspace check creation eligibility without reading dashboard documents. Embed tokens cannot use it.
- New-dashboard saves now enforce both the credential edit ceiling and the document policy. Contributors can still create under the default policy.
- The server requires contract
^0.5.0, keeping installed OpenAPI documentation aligned with the runtime.
A fresh registry install passed all 11 server exports and standalone SQLite/JWT permission checks. Deploy the server, host forwarding route and workspace in that order. This release does not complete Consumer browser or telemetry migration acceptance.
Dashboard packages v0.4.0 — Migration tools (2026-09-29)
Published compatible contract and server v0.4.0:
- Validate imported documents against the shared contract before any store access, including dry runs.
- Convert legacy planner requests using explicit connection/operation mappings while preserving widget bindings and document settings.
- Opt into
omitWhenEmptyfor optional filter arguments; keep existing binding behavior and host tenant controls. - Standalone servers enforce
allowedGroups; configure trusted JWT or ticket group mappings before upgrading restricted dashboards.
Upgrade both packages together. These migration capabilities do not replace live dashboard, filter and permission acceptance.
server v0.4.0 | contract v0.4.0
Dashboard packages v0.3.0 — Portable query execution (2026-09-29)
Published @microboxlabs/miot-dashboard-server and @microboxlabs/miot-dashboard-contract v0.3.0. Both packages are available on npm; dev migration acceptance remains open.
- The contract adds bounded connection-backed query definitions and named filter bindings while retaining version-2 document compatibility.
- The server exports TypeScript BigQuery and read-only HTTP executors under
/queries, with tenant checks, deadlines, cancellation, cost and response limits. - Embedded hosts supply a trusted resolver. The standalone image includes an operator module for ModularIoT’s private catalog; Java and Alfresco are not query execution requirements.
- Upgrade both packages together. Existing standalone deployments must explicitly configure an operations module to enable portable saved queries.
See the query guide and acceptance roadmap.
miot-calendar-client v0.8.0 — Time Window Blocks (2026-05-02)
@microboxlabs/miot-calendar-client — npm | GitHub
Adds typed support for distinguishing normal bookable time windows from non-bookable blocks.
Updated — client.calendars:
calendars.createTimeWindow()andcalendars.updateTimeWindow()acceptTimeWindowRequest.kind?: TimeWindowKind— useWINDOWfor bookable capacity orBLOCKfor closuresTimeWindowResponse.kind: TimeWindowKind— responses now identify whether each time window is a bookable window or a block
New types exported: TimeWindowKind
miot-calendar-client v0.7.0 — Time Window Colors (2026-05-02)
@microboxlabs/miot-calendar-client — npm | GitHub
Adds a time-window color field so planning UIs can persist and render calendar color selections through the API.
Updated — client.calendars:
TimeWindowRequest.color?: string— optional UI color token when creating or updating a time windowTimeWindowResponse.color?: string— optional UI color token returned with time-window data
miot-calendar-client v0.6.0 — Calendar Task Filters (2026-05-02)
@microboxlabs/miot-calendar-client — npm | GitHub
Adds calendar-level task filters and exposes SlotManager provisioning metadata for calendar configuration screens.
Updated — client.calendars:
CalendarRequest.filter?: CalendarFilter— persist task filters such asoriginanddestinationon a calendarCalendarRequest.autoSlotManager?: boolean— request default SlotManager provisioning when creating a calendarCalendarResponse.filter?: CalendarFilter— read the persisted task filter from calendar responsesCalendarResponse.hasSlotManager?: boolean— check whether a calendar has a SlotManager provisioned
New types exported: CalendarFilter
miot-calendar-client v0.3.0 — Slot Managers (2026-02-20)
@microboxlabs/miot-calendar-client — npm | GitHub
Adds a new Slot Managers resource for automating slot generation. Each manager keeps slots generated a configurable number of days in advance and can be triggered manually or by an external scheduler.
New — client.slotManagers namespace:
slotManagers.list({ active? })— list all slot managersslotManagers.create(body)— create a slot manager for a calendarslotManagers.get(id)— get a slot manager by IDslotManagers.update(id, body)— update configuration (including one-shot reprocessing)slotManagers.deactivate(id)— soft-delete a slot managerslotManagers.runAll()— trigger all active managers synchronouslyslotManagers.run(id)— trigger a single managerslotManagers.listAllRuns({ limit? })— list recent runs across all managersslotManagers.listRuns(id, { limit? })— list runs for a specific manager
New types exported: SlotManagerRequest, SlotManagerResponse, SlotManagerRunResponse
miot-calendar-client v0.2.0 — Calendar Groups (2026-02-19)
@microboxlabs/miot-calendar-client — npm | GitHub
Adds a new Calendar Groups resource that lets you organize calendars into named collections and filter or query them by group.
New — client.groups namespace:
groups.list({ active? })— list all groupsgroups.get(id)— get a group by IDgroups.create(body)— create a groupgroups.update(id, body)— update a groupgroups.deactivate(id)— soft-delete a group
Updated — client.calendars:
calendars.list()accepts a newgroupCodequery param to filter calendars by group membershipCalendarRequest.groups?: string[]— assign groups on create/update (null= no change,[]= remove all,["code"]= replace all)CalendarResponse.groups?: CalendarGroupResponse[]— groups the calendar belongs to are now included in the response
New types exported: CalendarGroupRequest, CalendarGroupResponse
Architecture: Centralized Sidebar Navigation (2026-02-19)
apps/app — internal change, no API impact
The sidebar navigation was refactored to use a single shared SidebarNavigationProvider context above both the desktop and mobile sidebar components.
What changed for operators:
- Badge counts on the desktop and mobile sidebar are now guaranteed to be identical — previously they could diverge because each sidebar fetched data independently
- User filter items under the Tasks section no longer duplicate after navigating between pages
What changed for developers:
- All navigation data (badge counts, dynamic task filter items) is fetched once per page load instead of twice
- The
pages.tsmodule constant is no longer mutated at runtime - New sections with dynamic sub-items can be added via
dynamicItemsSource+ a dedicated hook — see Extending Navigation
See ADR-001 for the full decision record.
v1.0.0 (Coming Soon)
Initial public release.
Features:
- Core telemetry ingestion
- Canonical metrics processing
- Basic symptom detection
- Control Tower dashboard
- REST API v1
- Multi-tenant support
Known Limitations:
- SDKs not yet available
- Limited symptom patterns
- Basic notification channels
Release Process
- Beta releases - Available to early access customers
- Minor releases - Bi-weekly on Tuesdays
- Major releases - Quarterly
Breaking Changes
Breaking changes are announced:
- 30 days advance notice minimum
- Migration guides provided
- Deprecation warnings in API
Feedback
Report issues and request features through your account representative or the support portal.