March 2026 Release

[madhavilosetty-intel]

March 2026 Release Checklist

Automated Component Releases

All component releases below are automated with dependency updates and version bumping

ui-toolkit (v3.3.12)

• Automated patch build triggered (dependency updates)
• npm package version auto-incremented

ui-toolkit-react (v5.0.3)

• Automated patch build triggered (dependency updates)
• @device-management-toolkit/ui-toolkit dependency updated to v3.3.12
• npm package version auto-incremented

ui-toolkit-angular (v11.1.3)

• @device-management-toolkit/ui-toolkit dependency updated to v3.3.12
• Automated patch build triggered (dependency updates)
• npm package version auto-incremented

wsman-messages (v6.0.1)

• Automated patch build triggered (dependency updates)
• npm package version auto-incremented

mps-router (v2.5.9)

• Automated patch build triggered (dependency updates)
• Docker image published to Docker Hub

go-wsman-messages (v2.38.1)

• Automated patch build triggered (dependency updates)
• Go library package published to pkg.go.dev

RPC-GO (v2.50.1)

• go-wsman-messages dependency updated to
• Docker image published to Docker Hub

Console (v1.22.9)

• go-wsman-messages dependency updated
• Sample-Web-UI dependency updated

RPS (v2.34.2)

• Package version auto-incremented
• @device-management-toolkit/wsman-messages dependency updated to v6.0.1
• Swagger API version updated
• Docker image published to Docker Hub

MPS (v2.26.4)

• Package version auto-incremented
• @device-management-toolkit/wsman-messages dependency updated to v6.0.1
• Swagger API version updated
• Docker image published to Docker Hub

Sample-Web-UI (v3.57.1)

• Package version auto-incremented
• @device-management-toolkit/ui-toolkit-angular dependency updated to latest
• Docker image published to Docker Hub

Manual Release Tasks

Cloud Deployment (March 2026 Release)

Manual tagging required for submodule coordination

• Verify database schema compatibility between MPS/RPS versions
• Update AzureDeploy.json if schema changes detected
• Tag all submodules with current release versions
• Create consolidated release tag
• Smoke test using docker compose

Documentation

• Update Release Notes with automated component versions
• Merge documentation PR
• Update mkdocs.yaml version to next release
• Update default version redirect in index.html
• Post release announcement on Discord
• Send release notification email