From 2c13a141b05d733fa4c0c3a30d8100f6cadc0d40 Mon Sep 17 00:00:00 2001 From: graikhel-intel Date: Tue, 30 Jun 2026 16:17:52 -0700 Subject: [PATCH] docs(release-notes): may 2026 release notes --- docs/Deployment/upgradeVersion.md | 10 +- docs/GetStarted/Cloud/buildRPC.md | 6 +- docs/GetStarted/Cloud/setup.md | 8 +- .../EA/RPSConfiguration/rpsConfiguration.md | 2 +- docs/Reference/faq.md | 81 ++-- docs/Reference/productionVault.md | 4 +- .../Scaling/Kubernetes/deployingk8s-aks.md | 12 +- .../Scaling/Kubernetes/deployingk8s-eks.md | 10 +- .../Scaling/Kubernetes/deployingk8s.md | 14 +- docs/Tutorials/Scaling/docker-swarm.md | 8 +- docs/release-notes.md | 365 +++--------------- mkdocs.yml | 26 +- site/index.html | 2 +- site/versions.json | 3 +- 14 files changed, 164 insertions(+), 387 deletions(-) diff --git a/docs/Deployment/upgradeVersion.md b/docs/Deployment/upgradeVersion.md index 673e05546..42fa737a6 100644 --- a/docs/Deployment/upgradeVersion.md +++ b/docs/Deployment/upgradeVersion.md @@ -509,7 +509,7 @@ Upgrading from a previous minor version to a new minor version release is simple ??? note "Note - Using Private Images" The steps are the same if using your own images built and stored on a platform like Azure Container Registry (ACR) or Elastic Container Registry (ECR). Simply point to the new private images rather than the public Intel Dockerhub. -1. Pull the latest release within `.\cloud-deployment` directory. +1. Pull the latest release within `.\deployment` directory. ``` git pull @@ -534,10 +534,10 @@ Upgrading from a previous minor version to a new minor version release is simple ... ``` -4. In Terminal or Command Prompt, go to the deployed cloud-deployment repository directory. +4. In Terminal or Command Prompt, go to the deployed `deployment` repository directory. ``` - cd ./YOUR-DIRECTORY-PATH/cloud-deployment + cd ./YOUR-DIRECTORY-PATH/deployment ``` 5. Use Helm to upgrade and deploy the new images. @@ -593,7 +593,7 @@ Is the functionality not working as expected? Rollback to the previous deploymen The following steps outline how to upgrade using the public Docker Hub images. Data will not be lost unless Postgres or Vault need to be upgraded and restarted. -1. From the `.\cloud-deployment\` directory, pull the latest branches. +1. From the `.\deployment\` directory, pull the latest branches. ``` git pull @@ -606,7 +606,7 @@ The following steps outline how to upgrade using the public Docker Hub images. D ``` ??? note "Note - Rebuilding New Images Locally" - If building your own images, you will also have to checkout the newer release from each repo within `.\cloud-deployment\`. + If building your own images, you will also have to checkout the newer release from each repo within `.\deployment\`. 1. Pull the new releases of the submodules. diff --git a/docs/GetStarted/Cloud/buildRPC.md b/docs/GetStarted/Cloud/buildRPC.md index 9cf95830c..6ac6069bb 100644 --- a/docs/GetStarted/Cloud/buildRPC.md +++ b/docs/GetStarted/Cloud/buildRPC.md @@ -46,12 +46,12 @@ Alternatively, the RPC-Go binaries can be manually built using Go for developmen If you are building an executable on a development system, you will copy the executable to the AMT device afterwards. -1. Change to the `rpc-go` directory of the cloned `cloud-deployment` repository. +1. Change to the `rpc-go` directory of the cloned `deployment` repository. ``` bash cd rpc-go ``` - ??? note "Haven't Cloned the `cloud-deployment` Repository?" + ??? note "Haven't Cloned the `deployment` Repository?" * Only clone the `rpc-go` repository: @@ -62,7 +62,7 @@ If you are building an executable on a development system, you will copy the exe * Alternatively, clone the whole toolkit repository: ``` bash - git clone https://github.com/device-management-toolkit/cloud-deployment --branch v{{ repoVersion.oamtct }} --recursive + git clone https://github.com/device-management-toolkit/deployment --branch v{{ repoVersion.oamtct }} --recursive ``` 2. Open a Terminal (Linux) or Powershell/Command Prompt **as Administrator** (Windows): diff --git a/docs/GetStarted/Cloud/setup.md b/docs/GetStarted/Cloud/setup.md index 13a0dfdbc..52d3b40c3 100644 --- a/docs/GetStarted/Cloud/setup.md +++ b/docs/GetStarted/Cloud/setup.md @@ -9,13 +9,13 @@ This setup runs the MPS and RPS microservices as Docker* containers, standardize 1. Open a Terminal or Command Prompt and navigate to a directory of your choice for development: ``` bash - git clone https://github.com/device-management-toolkit/cloud-deployment --branch v{{ repoVersion.oamtct }} --recursive + git clone https://github.com/device-management-toolkit/deployment --branch v{{ repoVersion.oamtct }} --recursive ``` -2. Change to the cloned `device-management-toolkit` directory. +2. Change to the cloned `deployment` directory. ``` bash - cd device-management-toolkit + cd deployment ``` ## Set Environment Variables @@ -140,7 +140,7 @@ Set the shared secret used in Kong for JWT authentication. !!! warning "Warning - Container Issues" - If any of the above containers are not running, walk through the steps again or file a GitHub issue [here]( https://github.com/device-management-toolkit/cloud-deployment/issues). + If any of the above containers are not running, walk through the steps again or file a GitHub issue [here]( https://github.com/device-management-toolkit/deployment/issues). If the Kong container reloads repeatedly, verify kong.yaml edits. Misconfiguration of this file will cause the container to reload. diff --git a/docs/Reference/EA/RPSConfiguration/rpsConfiguration.md b/docs/Reference/EA/RPSConfiguration/rpsConfiguration.md index 3eb833030..f5d80cb6a 100644 --- a/docs/Reference/EA/RPSConfiguration/rpsConfiguration.md +++ b/docs/Reference/EA/RPSConfiguration/rpsConfiguration.md @@ -23,7 +23,7 @@ The following services are assumed to be configured and running in your enterpri To use Enterprise Assistant with Kong API Gateway, we need to configure a new route. -2. Open the `kong.yaml` file in the `./cloud-deployment/` directory. +2. Open the `kong.yaml` file in the `./deployment/` directory. 3. Uncomment the `rps-ea` block to enable the `/ea` route. diff --git a/docs/Reference/faq.md b/docs/Reference/faq.md index 05af120b9..57d19e4d9 100644 --- a/docs/Reference/faq.md +++ b/docs/Reference/faq.md @@ -1,64 +1,85 @@ ## Frequently Asked Questions -### How are releases managed for Cloud-Deployment services in Device Management Toolkit? +### Why was the `cloud-deployment` repository renamed to `deployment`? -Cloud-Deployment services follows a Rolling Release model with the 2.x series, which also serves as our Long-Term Support (LTS) version. Each tagged release is kept up-to-date with the latest features, security fixes, and improvements. Customers benefit from continuous updates and support, ensuring a secure and feature-rich experience without the need to wait for separate release cycles. Currently, that is version 2.x. +The repository was renamed to better reflect its long-term direction. -We may decide to break off a 3.0 version at which point we will communicate support for 2.x at that time. +While the original focus was cloud deployments, the repository is evolving to support multiple deployment models, including both on-premises and cloud deployments, from a common deployment framework. -
+The current production deployment assets remain available on the [`v2` branch](https://github.com/device-management-toolkit/deployment/tree/v2), while new deployment capabilities are actively being developed on the `main` branch. -### How does versioning work with Cloud-Deployment services in Device Management Toolkit? + +### How are releases managed for the Deployment repository? + +The `deployment` repository follows a rolling release model. + +The current production deployment assets are maintained on the [`v2` branch](https://github.com/device-management-toolkit/deployment/tree/v2), which continues to receive updates, bug fixes, security improvements, and support for existing deployment scenarios. + +Development of the next generation deployment experience takes place on the `main` branch, where we are expanding support for both on-premises and cloud deployment models. As new capabilities mature, they will become part of future monthly releases. + +If we introduce a future major version, we will communicate the support lifecycle and migration guidance for existing deployments at that time. + + +### How does versioning work with the Deployment repository? Device Management Toolkit follows [SemVer](https://semver.org/) practices for versioning. This means: -- Major Version Increment - Breaking Changes (ex: 2.0.0 -> 3.0.0) -- Minor Version Increment - New Features (ex: 2.0.0 -> 2.1.0) -- Patch Version Increment - Security and Bug Fixes (ex: 2.0.0 -> 2.0.1) +- **Major Version Increment** - Breaking Changes (ex: 2.0.0 → 3.0.0) +- **Minor Version Increment** - New Features (ex: 2.0.0 → 2.1.0) +- **Patch Version Increment** - Security and Bug Fixes (ex: 2.0.0 → 2.0.1) All microservices with the same minor version should be compatible. -The separate repos for microservices and libraries are versioned individually. These versions are separate from the `cloud-deployment` repo version. The `cloud-deployment` repo is where we have the monthly release. This repo might carry a higher version than some of the individual repos but is tagged as `{Month} {Year}`. All sub-repos referenced within `cloud-deployment` for a specific release are guaranteed to be compatible. +Individual microservices and libraries continue to be versioned independently. + +The `deployment` repository itself is released monthly and tagged using the `{Month} {Year}` format. Each monthly release references a validated set of compatible component versions, ensuring all services work together as a supported deployment. -
-### What versions of Intel® AMT are supported? +### What versions of Intel® AMT are supported? -Device Management Toolkit aligns to the Intel Network and Edge (NEX) Group support roadmap for Intel vPro® Platform and Intel® AMT devices. This is currently calculated as `Latest AMT Version - 7`. +Device Management Toolkit aligns with the Intel Edge Computing Group support roadmap for Intel vPro® Platform and Intel® AMT devices. This is currently calculated as **Latest AMT Version - 7**. -
-### How do I migrate to a new release of Cloud-Deployment? +### How do I migrate to a new Deployment release? -Resources and information for migrating releases for either a Kubernetes deployment or local Docker deployment can be found in the [Upgrade Toolkit Version documentation](../Deployment/upgradeVersion.md). +Migration resources for both Kubernetes and local Docker deployments can be found in the [Upgrade Toolkit Version documentation](../Deployment/upgradeVersion.md). -
+The current production deployment assets are available on the [`v2` branch](https://github.com/device-management-toolkit/deployment/tree/v2). Future deployment capabilities will continue to be introduced through the `main` branch as they become available. -### Will there be any changes to Cloud-Deployment services following the release of Console v1.0? -No changes are currently planned. We will continue supporting our Cloud-Deployment services. +### What is the difference between the `v2` and `main` branches in the Deployment repository? -
+The [`v2` branch](https://github.com/device-management-toolkit/deployment/tree/v2) contains the current supported deployment assets and continues to receive updates, bug fixes, security improvements, and ongoing support. -### What is the long-term vision for MPS and RPS services following the release of Console v1.0? +The `main` branch is where new deployment capabilities are actively being developed, including support for both on-premises and cloud deployment scenarios. As these capabilities mature, they will become part of future monthly releases. -- Our long-term vision is for Console to support both Enterprise and Cloud deployments, reducing the number of services we need to maintain. -- As part of this vision, Console will take on the functions of both MPS and RPS. It will handle AMT connections and expose REST APIs to enable AMT features, similar to MPS. It will also manage profile creation, similar to RPS. -- Furthermore, RPC-Go will be utilized for the configuration and activation of AMT, improving efficiency and reducing the need for a full provisioning service on the backend. -- Consolidating these services into Console reduces our codebase and simplifies maintenance now with a smaller team. +Existing deployments should continue using the `v2` branch unless you are evaluating new functionality under active development. + + +### What is the long-term vision for MPS and RPS services? + +Our long-term vision is to simplify deployment by reducing the number of backend services required to manage Intel® AMT devices. + +Over time, Console will continue to absorb functionality currently provided by standalone services where it makes architectural and operational sense, while maintaining compatibility with existing deployment models during the transition. + +RPC-Go will continue evolving as the primary endpoint orchestration tool for Intel® AMT configuration, activation, and management, further simplifying deployment architectures and reducing the need for dedicated backend provisioning services. -
### What is a Pre-Release Feature? -Sometimes, newer features may be available as **pre-release**. These are features that are still in-development and subject to change. The team opts to make these available for early feedback. These may have limited functionality or potentially even bugs. When the feature is mature and fully validated, it will move from a **pre-release** state to a full release. +Sometimes, newer features may be available as **pre-release**. These are features that are still under development and subject to change. We make these available early to gather customer feedback and validate new functionality. + +Pre-release features may have limited functionality or known issues. Once they have matured and completed validation, they will transition to fully supported features. -
### How do I find more information about the MPS and RPS configuration files and security details? -Details and descriptions of configuration options can be found in [MPS Configuration](./MPS/configuration.md) and [RPS Configuration](./RPS/configuration.md). +Configuration documentation can be found here: + +- [MPS Configuration](./MPS/configuration.md) +- [RPS Configuration](./RPS/configuration.md) -Security information can be found in [MPS Security Information](./MPS/securityMPS.md) and [RPS Security Information](./RPS/securityRPS.md). +Security documentation can be found here: -
\ No newline at end of file +- [MPS Security Information](./MPS/securityMPS.md) +- [RPS Security Information](./RPS/securityRPS.md) \ No newline at end of file diff --git a/docs/Reference/productionVault.md b/docs/Reference/productionVault.md index 4f85cc912..5e8fe6eca 100644 --- a/docs/Reference/productionVault.md +++ b/docs/Reference/productionVault.md @@ -27,7 +27,7 @@ Learn how to run MPS and RPS using Vault in production server mode. The current entrypoint: vault server -config=/vault/config/vault.json ``` -3. Create a folder named `vault` located in `./cloud-deployment` directory and create a new file named `vault.json` in that folder with the contents below: +3. Create a folder named `vault` located in `./deployment` directory and create a new file named `vault.json` in that folder with the contents below: ```json { @@ -49,7 +49,7 @@ Learn how to run MPS and RPS using Vault in production server mode. The current } ``` -4. Run `docker compose` to start the containers from the ./cloud-deployment directory. +4. Run `docker compose` to start the containers from the ./deployment directory. ```bash docker compose up -d --build diff --git a/docs/Tutorials/Scaling/Kubernetes/deployingk8s-aks.md b/docs/Tutorials/Scaling/Kubernetes/deployingk8s-aks.md index 7a2f73bf6..b25385914 100644 --- a/docs/Tutorials/Scaling/Kubernetes/deployingk8s-aks.md +++ b/docs/Tutorials/Scaling/Kubernetes/deployingk8s-aks.md @@ -15,10 +15,10 @@ Azure Kubernetes Service (AKS) offers serverless Kubernetes, an integrated conti ## Get the Toolkit -1. Clone the cloud-deployment repository. +1. Clone the `deployment` repository. ``` - git clone https://github.com/device-management-toolkit/cloud-deployment.git --branch v{{ repoVersion.oamtct }} + git clone https://github.com/device-management-toolkit/deployment.git --branch v{{ repoVersion.oamtct }} ``` ## Create SSH Key @@ -46,7 +46,7 @@ This key is required by Azure to create VMs that use SSH keys for authentication az group create --name --location ``` -3. Provide the name of your new resource group from the last step and start a deployment at that resource group based on `aks.json` in the `./cloud-deployment` directory. +3. Provide the name of your new resource group from the last step and start a deployment at that resource group based on `aks.json` in the `./deployment` directory. ``` bash az deployment group create --resource-group --template-file aks.json @@ -86,7 +86,7 @@ Ensure your `kubectl` is connected to the Kubernetes cluster you wish to deploy/ ## Create Kubernetes Secrets -1. Open the `secrets.yaml` file in the `cloud-deployment/kubernetes/charts/` directory. +1. Open the `secrets.yaml` file in the `deployment/kubernetes/charts/` directory. ??? note "Note - Additional Information about Secrets Created" @@ -131,7 +131,7 @@ Ensure your `kubectl` is connected to the Kubernetes cluster you wish to deploy/ ### Edit values.yaml -1. Open the `values.yaml` file in `./cloud-deployment/kubernetes/charts/`. +1. Open the `values.yaml` file in `./deployment/kubernetes/charts/`. 2. Update the `service.beta.kubernetes.io/azure-dns-label-name` key in the **kong** section with a desired subdomain name for the URL that you would like for your cluster (i.e. myopenamtk8s). @@ -250,7 +250,7 @@ Ensure your `kubectl` is connected to the Kubernetes cluster you wish to deploy/ Add the root token as a secret to the AKS cluster so that the services can access Vault. -1. Open the `secrets.yaml` file again in the `cloud-deployment/kubernetes/charts/` directory. +1. Open the `secrets.yaml` file again in the `deployment/kubernetes/charts/` directory. 2. Replace `` in the `vaultKey:` field (line 66) with the actual Vault root token. diff --git a/docs/Tutorials/Scaling/Kubernetes/deployingk8s-eks.md b/docs/Tutorials/Scaling/Kubernetes/deployingk8s-eks.md index 024b9ffb4..cb12672aa 100644 --- a/docs/Tutorials/Scaling/Kubernetes/deployingk8s-eks.md +++ b/docs/Tutorials/Scaling/Kubernetes/deployingk8s-eks.md @@ -17,10 +17,10 @@ Amazon EKS offers serverless Kubernetes, an integrated continuous integration an ## Get the Toolkit -1. Clone the cloud-deployment repository. +1. Clone the `deployment` repository. ``` - git clone https://github.com/device-management-toolkit/cloud-deployment.git --branch v{{ repoVersion.oamtct }} + git clone https://github.com/device-management-toolkit/deployment.git --branch v{{ repoVersion.oamtct }} ``` ## Create a New EKS Cluster @@ -128,7 +128,7 @@ The Amazon EBS CSI plugin requires IAM permissions to make calls to Amazon APIs ``` ## Create Kubernetes Secrets -1. Open the `secrets.yaml` file in the `cloud-deployment/kubernetes/charts/` directory. +1. Open the `secrets.yaml` file in the `deployment/kubernetes/charts/` directory. ??? note "Note - Additional Information about Secrets Created" @@ -181,7 +181,7 @@ The Amazon EBS CSI plugin requires IAM permissions to make calls to Amazon APIs ### Edit values.yaml -1. Open the `values.yaml` file in the `./cloud-deployment/kubernetes/charts/` directory. +1. Open the `values.yaml` file in the `./deployment/kubernetes/charts/` directory. 2. Remove the **annotations** section and `service.beta.kubernetes.io/azure-dns-label-name` key in the `kong:` section. These are Azure-specific implementations. @@ -259,7 +259,7 @@ The Amazon EBS CSI plugin requires IAM permissions to make calls to Amazon APIs Add the root token as a secret to the AKS cluster so that the services can access Vault. -1. Open the `secrets.yaml` file again in the `cloud-deployment/kubernetes/charts/` directory. +1. Open the `secrets.yaml` file again in the `deployment/kubernetes/charts/` directory. 2. Replace `` in the `vaultKey:` field (line 66) with the actual Vault root token. diff --git a/docs/Tutorials/Scaling/Kubernetes/deployingk8s.md b/docs/Tutorials/Scaling/Kubernetes/deployingk8s.md index 1c71f6c00..b8494e2b3 100644 --- a/docs/Tutorials/Scaling/Kubernetes/deployingk8s.md +++ b/docs/Tutorials/Scaling/Kubernetes/deployingk8s.md @@ -24,10 +24,10 @@ Kubernetes, also known as K8s, is an open-source system for automating deploymen ### Build and Start - 1. Clone the cloud-deployment repository. + 1. Clone the deployment repository. ``` - git clone https://github.com/device-management-toolkit/cloud-deployment --branch v{{ repoVersion.oamtct }} + git clone https://github.com/device-management-toolkit/deployment --branch v{{ repoVersion.oamtct }} ``` 2. Copy the `.env.template` file to `.env`. @@ -86,16 +86,16 @@ Kubernetes, also known as K8s, is an open-source system for automating deploymen ## Get the Toolkit -1. Clone the cloud-deployment repository. +1. Clone the `deployment` repository. ``` - git clone https://github.com/device-management-toolkit/cloud-deployment.git --branch v{{ repoVersion.oamtct }} + git clone https://github.com/device-management-toolkit/deployment.git --branch v{{ repoVersion.oamtct }} ``` ## Create Kubernetes Secrets -1. Open the `secrets.yaml` file in the `cloud-deployment/kubernetes/charts/` directory. +1. Open the `secrets.yaml` file in the `deployment/kubernetes/charts/` directory. ??? note "Note - Additional Information about Secrets Created" @@ -143,7 +143,7 @@ Kubernetes, also known as K8s, is an open-source system for automating deploymen ### Edit values.yaml -1. Open the `values.yaml` file in `./cloud-deployment/kubernetes/charts/`. +1. Open the `values.yaml` file in `./deployment/kubernetes/charts/`. 2. Update the `commonName` key in the **mps** section with the IP Address of your development device. @@ -241,7 +241,7 @@ Kubernetes, also known as K8s, is an open-source system for automating deploymen Add the root token as a secret to the cluster so that the services can access Vault. -1. Open the `secrets.yaml` file again in the `cloud-deployment/kubernetes/charts/` directory. +1. Open the `secrets.yaml` file again in the `deployment/kubernetes/charts/` directory. 2. Replace `` in the `vaultKey:` field (line 66) with the actual Vault root token. diff --git a/docs/Tutorials/Scaling/docker-swarm.md b/docs/Tutorials/Scaling/docker-swarm.md index 4d8ce0525..607073438 100644 --- a/docs/Tutorials/Scaling/docker-swarm.md +++ b/docs/Tutorials/Scaling/docker-swarm.md @@ -4,7 +4,7 @@ This sample deployment demonstrates the use of Docker* in swarm mode. The follow - All images are built and tested with `docker compose`. To learn more about building the images with `docker compose`, refer to [**Express Setup**](../../GetStarted/Cloud/setup.md). - Push images to the registry to make them available for deployment on other systems. -- Run the commands below from the `cloud-deployment` install directory. +- Run the commands below from the `deployment` install directory. !!! important @@ -15,13 +15,13 @@ This sample deployment demonstrates the use of Docker* in swarm mode. The follow 1. Open a Terminal or Command Prompt and navigate to a directory of your choice for development: ``` bash - git clone --recursive https://github.com/device-management-toolkit/cloud-deployment --branch v{{ repoVersion.oamtct }} + git clone --recursive https://github.com/device-management-toolkit/deployment --branch v{{ repoVersion.oamtct }} ``` -2. Change to the cloned `cloud-deployment` directory. +2. Change to the cloned `deployment` directory. ``` bash - cd cloud-deployment + cd deployment ``` ## Deploy the stack to the swarm diff --git a/docs/release-notes.md b/docs/release-notes.md index 1efd7090d..b5254a4f3 100644 --- a/docs/release-notes.md +++ b/docs/release-notes.md @@ -1,16 +1,14 @@ - - # Release Notes !!! note "Note From the Team" - This release includes several enhancements across Console, RPS, RPC-Go, and supporting libraries, including the official release of end-to-end TLS support between Intel AMT and RPS, MongoDB support for Console, wireless state APIs, container health checks, provisioning certificate validation improvements, and continued investments in the rpc-go v3 experience. + This release marks the beginning of the next evolution of our deployment experience. As part of this effort, the `cloud-deployment` repository has been renamed to `deployment` to better reflect its long-term direction of supporting both on-premises and cloud deployments from a common deployment framework. - End-to-end TLS communication between Intel AMT and RPS is now considered production-ready and officially supported. Over the last several releases, we have continued to improve certificate validation, TLS tunnel reliability, TLS rollover behavior, and compatibility across different Intel AMT versions to support this milestone. + The current production deployment assets remain available on the [`v2` branch](https://github.com/device-management-toolkit/deployment/tree/v2), which continues to be supported for existing deployments. New deployment capabilities and features are being developed on the `main` branch as we continue expanding Console support for both cloud and on-premises deployment scenarios. You can follow the latest work here: https://github.com/device-management-toolkit/deployment. - We also made significant progress on rpc-go v3 with improvements to the CLI experience, richer device information, expanded certificate visibility, HTTP proxy configuration support, improved activation workflows, and better supportability features. Additional enhancements are already in development and will continue rolling out over the next few releases. + This release also introduces a random administrator password during Console setup, continues the rollout of discovery and wireless profile management capabilities, and includes several quality improvements across Console, RPC-Go, Go WSMAN Messages, and the Sample Web UI. - In upcoming releases, you should start seeing support for Intel AMT 22 platforms, additional wireless management capabilities in Console, continued rpc-go v3 improvements, installer enhancements, discovery improvements, and further investments in certificate and provisioning workflows. + In upcoming releases, you will continue to see investments in deployment capabilities, expanded discovery information (OS details such as OS version, CPU model, and network adapters; AMT fields such as TLS mode and DHCP status; and hardware insights like monitor detection), wireless profile management, AMT 22 platform support, installer enhancements, and additional device management capabilities across the toolkit. Follow our [Sprint Board](https://github.com/orgs/device-management-toolkit/projects/10/views/2) to learn more and track upcoming features. @@ -21,73 +19,52 @@ ## 🚀 What's New? -### RPS & RPC-Go: End-to-End TLS Support for Intel AMT - -This release officially supports end-to-end TLS communication between Intel AMT and RPS using the `-tls-tunnel` flag in rpc-go. - -As part of this flow, RPS creates a new Intel AMT TLS leaf certificate signed by the existing MPS Root Certificate. Intel AMT then uses that certificate for the TLS session with RPS. - -The AMT private key always remains within Intel AMT and is never exposed to rpc-go or the host OS. rpc-go only proxies the encrypted TLS traffic between Intel AMT and RPS, so the TLS session is not decrypted on the device. +### Deployment Repository: Expanded Beyond Cloud Deployments -This capability is now considered production-ready and officially supported. +The `cloud-deployment` repository has been renamed to `deployment` to better reflect its long-term direction. The repository is evolving to support multiple deployment models, including both on-premises and cloud deployments, from a common deployment framework. -### RPC-Go v3: Improved CLI Experience and Device Information +The current production deployment assets remain available on the [`v2` branch](https://github.com/device-management-toolkit/deployment/tree/v2), which continues to be supported for existing deployments. New deployment capabilities and features, however, are being developed on the `main` branch as Console expands its support for both cloud and on-premises deployment scenarios. -This release includes several improvements to the rpc-go v3 user experience, including a redesigned `amtinfo` command with improved formatting, richer device information, expanded certificate visibility, and support for viewing Intel AMT HTTP proxy configuration. +You can follow the latest deployment work in the `main` branch [here](https://github.com/device-management-toolkit/deployment). -The updated output provides a more structured view of device configuration, network adapters, remote access settings, certificates, and other platform information, making troubleshooting and device validation easier for administrators. +### Console: Random Administrator Password on First Run -Additional improvements include a more detailed `version` command for troubleshooting and supportability, the ability to launch from a non-administrator terminal and elevate only when required, and enhancements to activation workflows for local profile-based deployments. +Console now generates a random administrator password during the initial setup, ensuring each installation starts with a unique administrator credential. -### Console: MongoDB Database Support +Users can update the generated password to a password of their choice as part of their normal deployment and security practices. -Console now supports MongoDB as an alternative database backend. This provides organizations with additional deployment flexibility and enables environments that prefer document-based storage to run Console without requiring PostgreSQL. +### Console & RPC-Go v3 (Beta): Discovery Improvements -### Console: Health Checks for Containerized Deployments +Support has been added for capturing Intel LMS installation status during device registration when using rpc-go v3 (Beta). Rpc-go v3 detects the presence of Intel LMS on the endpoint, and Console stores this information as part of the device details. -Console now includes a CLI health check command designed for containerized deployments. This simplifies readiness and health monitoring when running Console in Docker, Kubernetes, and other orchestration environments. +This is the first of several planned discovery enhancements that will continue to expand the device information and health insights available in Console over the coming releases. -### RPS: Provisioning Certificate Validation +### Go WSMAN Messages: Wireless Profile Management -RPS now validates provisioning certificates before activation begins, helping identify invalid or unsupported certificates earlier in the provisioning workflow and reducing activation failures. - -### Console: Wireless API - -Console now includes APIs to query and manage wireless state information, providing a foundation for upcoming wireless management capabilities in Console. +The Go WSMAN Messages library now includes the underlying support for Intel AMT WiFi profile management. In upcoming releases, these capabilities will be surfaced through new Console APIs and user interface enhancements, making wireless profile management easier and more intuitive. ## 🧩 Enhancements & Improvements -### Console: Improved Request Handling - -Console now supports cancellation of in-flight requests, helping prevent stale operations from continuing in the background and improving responsiveness during long-running device operations. +### Console: OAuth Configuration Improvements -### Go WSMAN Messages: Expanded CIM, AMT, and IPS Coverage +Console now supports additional `AUTH_*` environment variables for OAuth configuration beyond the configuration file, providing greater flexibility when deploying Console in containerized and cloud environments. -The Go WSMAN Messages library continues to expand its coverage of Intel AMT, CIM, and IPS resources, adding support for CIM_Battery, CIM_Fan, and CIM_Sensor classes based on customer feedback. +This is one of several ongoing improvements to support the evolving deployment architecture. Additional deployment capabilities and documentation will continue to be added to the `deployment` repository over the coming releases. -In addition to the new CIM, AMT, and IPS service wrappers, significant internal improvements were made to reduce code duplication, improve maintainability, and simplify the process of extending WSMAN service support in future releases. +### Console: Platform Information Improvements -### Sample Web UI: Faster KVM Session Connection +Console now retrieves processor information using Enumerate/Pull operations, more accurately reports KVM availability after AMT feature configuration, and launches the browser using the configured Console host. -The KVM connection initialization sequence has been optimized, reducing the time from clicking "Connect KVM" to seeing the remote desktop. ## 🔧 Fixes & Maintenance -- RPS fixes for legacy TLS compatibility, TLS rollover reliability, post-TLS validation behavior, and certificate serial number generation - -- RPC-Go fix to correctly handle TLS 1.3 data received from Intel AMT - -- MPS validation improvements for DNS suffix configuration +- RPC-Go fix to gracefully handle busy Intel ME watchdog (HECI) clients during `amtinfo` -- Console fixes for request cancellation handling, profile updates, OpenAPI specification updates, PostgreSQL compatibility, CIRA configuration handling, redirection token expiration, certificate generation, configuration path resolution, and general API stability +- Sample Web UI fixes for Intel AMT feature selection persistence and AUTH_MODE parsing -- Console fixes to improve profile validation and allow profile updates without re-entering passwords +- Go WSMAN Messages fixes for WiFi profile updates and UEFI WiFi profile handling -- Sample Web UI fixes for profile editing, certificate list refresh behavior, WSMAN Explorer UI behavior, and password handling improvements - -- Go WSMAN Messages fixes for APF channel cleanup, channel lifecycle management, and event-driven response handling - -- UI Toolkit fix to release held keyboard keys when KVM sessions lose focus +- RPC-Go v3 (Beta) fixes for activation workflows, including CCM activation and local profile activation - Minor dependency updates and general maintenance across toolkit components @@ -95,336 +72,114 @@ The KVM connection initialization sequence has been optimized, reducing the time ### RPS -#### [2.36.4](https://github.com/device-management-toolkit/rps/compare/v2.36.3...v2.36.4) (2026-05-26) - -Bug Fixes - -* **api:** allow profile PATCH without passwords ([#2715](https://github.com/device-management-toolkit/rps/issues/2715)) ([7d77f64](https://github.com/device-management-toolkit/rps/commit/7d77f641e5a50cd2a384f145d5d6f4149fd0221e)) - -#### [2.36.3](https://github.com/device-management-toolkit/rps/compare/v2.36.2...v2.36.3) (2026-05-11) - -Bug Fixes - -* harden post CCM TLS rollover and retry behavior ([#2691](https://github.com/device-management-toolkit/rps/issues/2691)) ([0576cca](https://github.com/device-management-toolkit/rps/commit/0576ccaec4c98dd00149df94e86da248b9899992)) - -#### [2.36.2](https://github.com/device-management-toolkit/rps/compare/v2.36.1...v2.36.2) (2026-04-30) - -Bug Fixes - -* address negative serial numbers generated ~20% of the time ([#2690](https://github.com/device-management-toolkit/rps/issues/2690)) ([aa30c80](https://github.com/device-management-toolkit/rps/commit/aa30c80eafb33f9c9a92de9a0366020f2587c1e0)) - -#### [2.36.1](https://github.com/device-management-toolkit/rps/compare/v2.36.0...v2.36.1) (2026-04-29) - -Bug Fixes - -* enable AMT legacy TLS compatibility and post-TLS reject by default ([#2689](https://github.com/device-management-toolkit/rps/issues/2689)) ([b9d4397](https://github.com/device-management-toolkit/rps/commit/b9d43976d8902de930bd57406e674fba8afeb3d2)) - -#### [2.36.0](https://github.com/device-management-toolkit/rps/compare/v2.35.0...v2.36.0) (2026-04-28) - -Features - -* improves tls tunnel flow ([#2683](https://github.com/device-management-toolkit/rps/issues/2683)) ([652d2bf](https://github.com/device-management-toolkit/rps/commit/652d2bf3997e06dd7ce8246954fc1fe494126428)) - -#### [2.35.0](https://github.com/device-management-toolkit/rps/compare/v2.34.3...v2.35.0) (2026-04-24) - -Features - -* add provisioning certificate validation checks ([#2686](https://github.com/device-management-toolkit/rps/issues/2686)) ([e473dda](https://github.com/device-management-toolkit/rps/commit/e473dda72429879f536aa6584287c7ee4917c8b0)) - -#### [2.34.3](https://github.com/device-management-toolkit/rps/compare/v2.34.2...v2.34.3) (2026-04-22) - -Performance Improvements - -* improves rpc to rps performance ([#2681](https://github.com/device-management-toolkit/rps/issues/2681)) ([79f9a53](https://github.com/device-management-toolkit/rps/commit/79f9a5370d518d79efbe7aeec8048d3dd6e9bb52)) +#### [2.36.5](https://github.com/device-management-toolkit/rps/compare/v2.36.4...v2.36.5) (2026-06-03) ### MPS -#### [2.26.6](https://github.com/device-management-toolkit/mps/compare/v2.26.5...v2.26.6) (2026-05-20) - -#### [2.26.5](https://github.com/device-management-toolkit/mps/compare/v2.26.4...v2.26.5) (2026-04-21) - -Bug Fixes - -* added input validator for dnsSuffix ([#2393](https://github.com/device-management-toolkit/mps/issues/2393)) ([355bb85](https://github.com/device-management-toolkit/mps/commit/355bb8540577db7c87c85dfcc88f6119fb5470fd)) +#### [2.26.7](https://github.com/device-management-toolkit/mps/compare/v2.26.6...v2.26.7) (2026-06-03) ### RPC Go -#### [2.50.6](https://github.com/device-management-toolkit/rpc-go/compare/v2.50.5...v2.50.6) (2026-05-21) - -#### [2.50.5](https://github.com/device-management-toolkit/rpc-go/compare/v2.50.4...v2.50.5) (2026-05-14) - -#### [2.50.4](https://github.com/device-management-toolkit/rpc-go/compare/v2.50.3...v2.50.4) (2026-04-29) - -Bug Fixes - -* ensure latest go version is used ([#1298](https://github.com/device-management-toolkit/rpc-go/issues/1298)) ([494cd77](https://github.com/device-management-toolkit/rpc-go/commit/494cd77ffbe8ce50a72148ae52e938f6a6c9f54a)) - -#### [2.50.3](https://github.com/device-management-toolkit/rpc-go/compare/v2.50.2...v2.50.3) (2026-04-29) - -Bug Fixes - -* ensure semantic release uses latest version of go ([2251071](https://github.com/device-management-toolkit/rpc-go/commit/225107155c8f2121d2cd486acc198e91eaa4f358)) +#### [2.50.8](https://github.com/device-management-toolkit/rpc-go/compare/v2.50.7...v2.50.8) (2026-06-03) -#### [2.50.2](https://github.com/device-management-toolkit/rpc-go/compare/v2.50.1...v2.50.2) (2026-04-28) +#### [2.50.7](https://github.com/device-management-toolkit/rpc-go/compare/v2.50.6...v2.50.7) (2026-05-28) Bug Fixes -* handle tls v1.3 data from AMT ([56bc354](https://github.com/device-management-toolkit/rpc-go/commit/56bc3545d3f21ed7a53c5ce27f894be6661d0949)) +* handle busy watchdog HECI client in amtinfo ([#1343](https://github.com/device-management-toolkit/rpc-go/issues/1343)) ([b473599](https://github.com/device-management-toolkit/rpc-go/commit/b473599ef87ec8202ff9f5473f2296581714f89d)) ### Sample Web UI -#### [3.57.7](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.6...v3.57.7) (2026-05-26) - -Bug Fixes - -* require password when switching random to static on edit ([#3334](https://github.com/device-management-toolkit/sample-web-ui/issues/3334)) ([f262b20](https://github.com/device-management-toolkit/sample-web-ui/commit/f262b20bd71f6236cbc316df6416ed5ee1788658)) - -#### [3.57.6](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.5...v3.57.6) (2026-05-22) +#### [3.57.10](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.9...v3.57.10) (2026-06-03) -Bug Fixes - -* correct malformed translate interpolation on proxy label ([#3331](https://github.com/device-management-toolkit/sample-web-ui/issues/3331)) ([82431b2](https://github.com/device-management-toolkit/sample-web-ui/commit/82431b29ccff9f7bfc49076242f16a79b78e8dac)) - -#### [3.57.5](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.4...v3.57.5) (2026-05-20) - -#### [3.57.4](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.3...v3.57.4) (2026-05-20) +#### [3.57.9](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.8...v3.57.9) (2026-05-27) Bug Fixes -* devices: bind WSMAN Explorer placeholder via property syntax ([#3320](https://github.com/device-management-toolkit/sample-web-ui/issues/3320)) ([2473592](https://github.com/device-management-toolkit/sample-web-ui/commit/2473592605bc593137632b99922dcc6e5e7d9b8f)), closes [#3319](https://github.com/device-management-toolkit/sample-web-ui/issues/3319) -* devices: refresh certificate list immediately on add and delete ([#3318](https://github.com/device-management-toolkit/sample-web-ui/issues/3318)) ([5874a05](https://github.com/device-management-toolkit/sample-web-ui/commit/5874a05a47a78c5046dfac5e2cc7d715adc667bb)), closes [#3317](https://github.com/device-management-toolkit/sample-web-ui/issues/3317) +* ensure amt features remain selected upon form re-entry ([#3343](https://github.com/device-management-toolkit/sample-web-ui/issues/3343)) ([e376bd5](https://github.com/device-management-toolkit/sample-web-ui/commit/e376bd5f604f27f326c88652052a4f7450aed809)) -#### [3.57.3](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.2...v3.57.3) (2026-05-15) +#### [3.57.8](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.7...v3.57.8) (2026-05-26) Bug Fixes -* allow editing profile without re-entering passwords ([#3307](https://github.com/device-management-toolkit/sample-web-ui/issues/3307)) ([4df57b2](https://github.com/device-management-toolkit/sample-web-ui/commit/4df57b2723c20a594cd2d5ec34c0f975c4916567)) - -#### [3.57.2](https://github.com/device-management-toolkit/sample-web-ui/compare/v3.57.1...v3.57.2) (2026-04-22) - -Performance Improvements - -* improve KVM connection time ([f97baa2](https://github.com/device-management-toolkit/sample-web-ui/commit/f97baa2ab933b57990faa9a4c124510698135273)) +* correctly parse AUTH_MODE_ENABLED ([#3329](https://github.com/device-management-toolkit/sample-web-ui/issues/3329)) ([f4a6f9b](https://github.com/device-management-toolkit/sample-web-ui/commit/f4a6f9b4739ecdd0e93ec7b5dee952ac65a8d735)) ### UI Toolkit -#### [3.3.15](https://github.com/device-management-toolkit/ui-toolkit/compare/v3.3.14...v3.3.15) (2026-05-20) - -#### [3.3.14](https://github.com/device-management-toolkit/ui-toolkit/compare/v3.3.13...v3.3.14) (2026-05-19) - -Bug Fixes - -* build: restore dist/core/package.json subpath shim ([218930f](https://github.com/device-management-toolkit/ui-toolkit/commit/218930f2d02904afbe28e878578a1687a505b070)) - -#### [3.3.13](https://github.com/device-management-toolkit/ui-toolkit/compare/v3.3.12...v3.3.13) (2026-05-19) - -Bug Fixes - -* kvm: release held keys on blur ([#1696](https://github.com/device-management-toolkit/ui-toolkit/issues/1696)) ([5629ca1](https://github.com/device-management-toolkit/ui-toolkit/commit/5629ca1e48c66dc3bc6d525492d59b6f68a43dc9)) +#### [3.3.16](https://github.com/device-management-toolkit/ui-toolkit/compare/v3.3.15...v3.3.16) (2026-06-03) ### UI Toolkit Angular -#### [11.1.4](https://github.com/device-management-toolkit/ui-toolkit-angular/compare/v11.1.3...v11.1.4) (2026-05-20) +#### [11.1.5](https://github.com/device-management-toolkit/ui-toolkit-angular/compare/v11.1.4...v11.1.5) (2026-06-03) ### UI Toolkit React -#### [5.0.4](https://github.com/device-management-toolkit/ui-toolkit-react/compare/v5.0.3...v5.0.4) (2026-05-20) +#### [5.0.5](https://github.com/device-management-toolkit/ui-toolkit-react/compare/v5.0.4...v5.0.5) (2026-06-03) ### Console -#### [1.27.2](https://github.com/device-management-toolkit/console/compare/v1.27.1...v1.27.2) (2026-05-20) +#### [1.29.1](https://github.com/device-management-toolkit/console/compare/v1.29.0...v1.29.1) (2026-06-04) -#### [1.27.1](https://github.com/device-management-toolkit/console/compare/v1.27.0...v1.27.1) (2026-05-19) - -Reverts - -* Revert "fix: correct inverted GIN_MODE condition in handleDebugMode ([#979](https://github.com/device-management-toolkit/console/pull/979))" ([d8d9ef0](https://github.com/device-management-toolkit/console/commit/d8d9ef028f8a8e482998acdc49f2e92f5305c925)), closes [#979](https://github.com/device-management-toolkit/console/issues/979) - -#### [1.27.0](https://github.com/device-management-toolkit/console/compare/v1.26.6...v1.27.0) (2026-05-18) +#### [1.29.0](https://github.com/device-management-toolkit/console/compare/v1.28.1...v1.29.0) (2026-06-01) Features -* tray: enforce single instance and expose reachable URLs ([676bd75](https://github.com/device-management-toolkit/console/commit/676bd75bfc3f7d656cd429dc80de01e5032890ea)), closes [#870](https://github.com/device-management-toolkit/console/issues/870) +* store lmsInstalled in deviceInfo JSON column ([#905](https://github.com/device-management-toolkit/console/issues/905)) ([f01cb2b](https://github.com/device-management-toolkit/console/commit/f01cb2b4f599dad6a215a5574cc9e44fb8f23e1c)), closes [device-management-toolkit/rpc-go#1246](https://github.com/device-management-toolkit/rpc-go/issues/1246) -#### [1.26.6](https://github.com/device-management-toolkit/console/compare/v1.26.5...v1.26.6) (2026-05-18) +#### [1.28.1](https://github.com/device-management-toolkit/console/compare/v1.28.0...v1.28.1) (2026-05-27) Bug Fixes -* config: resolve symlinks when locating config dir ([#985](https://github.com/device-management-toolkit/console/issues/985)) ([3c696e6](https://github.com/device-management-toolkit/console/commit/3c696e6e5a7fd968dc65c86a6cbbe02da2d3fe4b)) +* ensure kvmavailable is returned accurately upon amtfeature set ([#1030](https://github.com/device-management-toolkit/console/issues/1030)) ([1d0d432](https://github.com/device-management-toolkit/console/commit/1d0d432092966454da72f54aad29901002d7a89b)) -#### [1.26.5](https://github.com/device-management-toolkit/console/compare/v1.26.4...v1.26.5) (2026-05-18) - -Bug Fixes - -* cert generation returns parsed cert with valid Raw field ([#970](https://github.com/device-management-toolkit/console/issues/970)) ([9d06967](https://github.com/device-management-toolkit/console/commit/9d06967160dc155006380c14cc01d29c9f39aa90)), closes [device-management-toolkit/deployment#573](https://github.com/device-management-toolkit/deployment/issues/573) - -#### [1.26.4](https://github.com/device-management-toolkit/console/compare/v1.26.3...v1.26.4) (2026-05-18) - -Bug Fixes - -* correct inverted GIN_MODE condition in handleDebugMode ([#979](https://github.com/device-management-toolkit/console/issues/979)) ([8bb7d69](https://github.com/device-management-toolkit/console/commit/8bb7d6966b5a09aed113bd6d9e60cd61c906698d)), closes [device-management-toolkit/deployment#573](https://github.com/device-management-toolkit/deployment/issues/573) - -#### [1.26.3](https://github.com/device-management-toolkit/console/compare/v1.26.2...v1.26.3) (2026-05-15) - -Bug Fixes - -* api: allow profile PATCH without passwords ([#973](https://github.com/device-management-toolkit/console/issues/973)) ([18ba76d](https://github.com/device-management-toolkit/console/commit/18ba76dfb6c41f5e394f9ba31de9583be5f48dd3)) - -#### [1.26.2](https://github.com/device-management-toolkit/console/compare/v1.26.1...v1.26.2) (2026-05-12) - -Bug Fixes - -* enforce RPS profile name and password rules on /profiles ([#963](https://github.com/device-management-toolkit/console/issues/963)) ([b484704](https://github.com/device-management-toolkit/console/commit/b48470444e94fd7bbb62fbcd7388a98f9629ac13)) - -#### [1.26.1](https://github.com/device-management-toolkit/console/compare/v1.26.0...v1.26.1) (2026-05-12) - -Bug Fixes - -* fix redirection token expiration ([#958](https://github.com/device-management-toolkit/console/issues/958)) ([2985470](https://github.com/device-management-toolkit/console/commit/29854706461e4d9fc3fdc5e86fa8dd38d7ee3047)) - -#### [1.26.0](https://github.com/device-management-toolkit/console/compare/v1.25.2...v1.26.0) (2026-05-06) +#### [1.28.0](https://github.com/device-management-toolkit/console/compare/v1.27.5...v1.28.0) (2026-05-27) Features -* add MongoDB NoSQL database backend ([#904](https://github.com/device-management-toolkit/console/issues/904)) ([e4e33d2](https://github.com/device-management-toolkit/console/commit/e4e33d2a662f73788cb7583141d67451d5b78d3a)) +* adds support for randomly generated admin password on first run ([d60f24c](https://github.com/device-management-toolkit/console/commit/d60f24c96d24f63c230f3bd219106a8dfd822993)) -#### [1.25.2](https://github.com/device-management-toolkit/console/compare/v1.25.1...v1.25.2) (2026-05-06) +#### [1.27.5](https://github.com/device-management-toolkit/console/compare/v1.27.4...v1.27.5) (2026-05-27) Bug Fixes -* remove postgres-only IF NOT EXISTS from ALTER TABLE ([#953](https://github.com/device-management-toolkit/console/issues/953)) ([45c1686](https://github.com/device-management-toolkit/console/commit/45c168630551131425aed50c088e4f162ad51282)) +* fetch processor info via Enumerate/Pull instead of Get ([#1028](https://github.com/device-management-toolkit/console/issues/1028)) ([6d891f3](https://github.com/device-management-toolkit/console/commit/6d891f3d6eadeb18aad7c2856e7dba7b908a46d3)) -#### [1.25.1](https://github.com/device-management-toolkit/console/compare/v1.25.0...v1.25.1) (2026-05-05) +#### [1.27.4](https://github.com/device-management-toolkit/console/compare/v1.27.3...v1.27.4) (2026-05-25) Bug Fixes -* ensure postgres works with ciraconfigs ([#950](https://github.com/device-management-toolkit/console/issues/950)) ([f3690c5](https://github.com/device-management-toolkit/console/commit/f3690c58980ac092727985f2f333d419265815ca)) - -#### [1.25.0](https://github.com/device-management-toolkit/console/compare/v1.24.4...v1.25.0) (2026-05-05) - -Features - -* enables healthcheck via cli for containerized deployments ([#949](https://github.com/device-management-toolkit/console/issues/949)) ([f5975ba](https://github.com/device-management-toolkit/console/commit/f5975ba867629277a4f8da473f9cd19da5a2f6dd)) - -#### [1.24.4](https://github.com/device-management-toolkit/console/compare/v1.24.3...v1.24.4) (2026-05-05) - -Bug Fixes - -* address small issues ([#948](https://github.com/device-management-toolkit/console/issues/948)) ([10877dd](https://github.com/device-management-toolkit/console/commit/10877dd020fddf6c94f2fb0eb77f54c60637c08c)) - -#### [1.24.3](https://github.com/device-management-toolkit/console/compare/v1.24.2...v1.24.3) (2026-04-30) - -Bug Fixes - -* preserve omitted fields on PATCH ([#917](https://github.com/device-management-toolkit/console/issues/917)) ([e86bdd8](https://github.com/device-management-toolkit/console/commit/e86bdd80eb1bfa667e702a4251130b5989d98114)) - -#### [1.24.2](https://github.com/device-management-toolkit/console/compare/v1.24.1...v1.24.2) (2026-04-29) - -Bug Fixes - -* update openapi spec ([#915](https://github.com/device-management-toolkit/console/issues/915)) ([1d2f1ce](https://github.com/device-management-toolkit/console/commit/1d2f1cec58bb2532a6f039489c5c7c81aec80719)) - -#### [1.24.1](https://github.com/device-management-toolkit/console/compare/v1.24.0...v1.24.1) (2026-04-28) - -Bug Fixes - -* serve full monaco asset subtree for Explorer ([#911](https://github.com/device-management-toolkit/console/issues/911)) ([abbc036](https://github.com/device-management-toolkit/console/commit/abbc036ba70b96012c2befa2267ef4ebcd470ecd)) - -#### [1.24.0](https://github.com/device-management-toolkit/console/compare/v1.23.2...v1.24.0) (2026-04-28) - -Features - -* add wireless state get and request API ([#885](https://github.com/device-management-toolkit/console/issues/885)) ([ccd254c](https://github.com/device-management-toolkit/console/commit/ccd254c62bb543c29cd22d3efa75c418074a4b96)) - -#### [1.23.2](https://github.com/device-management-toolkit/console/compare/v1.23.1...v1.23.2) (2026-04-23) +* default browser launch host to configured host ([#1015](https://github.com/device-management-toolkit/console/issues/1015)) ([5a076ce](https://github.com/device-management-toolkit/console/commit/5a076cef2bb0bd09e640ce613871f8d011445451)) -#### [1.23.1](https://github.com/device-management-toolkit/console/compare/v1.23.0...v1.23.1) (2026-04-22) +#### [1.27.3](https://github.com/device-management-toolkit/console/compare/v1.27.2...v1.27.3) (2026-05-22) Bug Fixes -* address issue with calls failing after being cancelled ([3067bb8](https://github.com/device-management-toolkit/console/commit/3067bb863962cb91836b3abf8b73d845be827e7f)) - -#### [1.23.0](https://github.com/device-management-toolkit/console/compare/v1.22.9...v1.23.0) (2026-04-16) - -Features - -* enable cancelling of requests ([92f6575](https://github.com/device-management-toolkit/console/commit/92f65759fbe4f01eb72f85bb42d6b85d7b2b7cf3)) +* allow AUTH_ env vars for OAuth Configuration beyond just config ([5e11665](https://github.com/device-management-toolkit/console/commit/5e116650985e188142fef17933cfd095d2d29cf0)) ### Go WSMAN Messages -#### [2.46.1](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.46.0...v2.46.1) (2026-05-20) - -#### [2.46.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.45.0...v2.46.0) (2026-05-12) - -Features - -* cim: add CIM_Battery service ([#692](https://github.com/device-management-toolkit/go-wsman-messages/issues/692)) ([469d11d](https://github.com/device-management-toolkit/go-wsman-messages/commit/469d11d2f6d8c230b77eaa4ae8a6172c0c9dc47d)) - -#### [2.45.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.44.0...v2.45.0) (2026-05-12) - -Features - -* cim: add fan sensor ([#693](https://github.com/device-management-toolkit/go-wsman-messages/issues/693)) ([c59d02d](https://github.com/device-management-toolkit/go-wsman-messages/commit/c59d02dcb66f4483a7c3daa13666f6fcb7423c5c)) - -#### [2.44.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.43.0...v2.44.0) (2026-05-12) - -Features - -* cim: add CIM_Sensor service ([#691](https://github.com/device-management-toolkit/go-wsman-messages/issues/691)) ([9477280](https://github.com/device-management-toolkit/go-wsman-messages/commit/9477280110e2eab79c4fc918be84306fc1563a10)) - -#### [2.43.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.42.0...v2.43.0) (2026-04-29) - -Features - -* add CIM_AssociatedPowerManagementService wrapper ([#679](https://github.com/device-management-toolkit/go-wsman-messages/issues/679)) ([2fc831a](https://github.com/device-management-toolkit/go-wsman-messages/commit/2fc831a4c4b461598688c33afa2eb778fe47e155)) - -#### [2.42.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.41.0...v2.42.0) (2026-04-29) - -Features - -* add missing wsman fetcher class function ([#664](https://github.com/device-management-toolkit/go-wsman-messages/issues/664)) ([8dd142f](https://github.com/device-management-toolkit/go-wsman-messages/commit/8dd142fc89ae5c3484ff562f77d6ceebbdede274)) - -#### [2.41.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.40.0...v2.41.0) (2026-04-29) - -Features - -* add missing wsman fetcher class function for CIM classes ([#681](https://github.com/device-management-toolkit/go-wsman-messages/issues/681)) ([75f8a82](https://github.com/device-management-toolkit/go-wsman-messages/commit/75f8a82f7bf50dacbd5e91d536dba26cdb47a015)) - -#### [2.40.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.39.0...v2.40.0) (2026-04-29) - -Features - -* add missing wsman fetcher class function for IPS Classes ([#671](https://github.com/device-management-toolkit/go-wsman-messages/issues/671)) ([61db8da](https://github.com/device-management-toolkit/go-wsman-messages/commit/61db8dab4a0d52a26040a76b8876332fd2a4bb8c)) - -#### [2.39.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.38.4...v2.39.0) (2026-04-17) - -Features - -* amt/boot: add RPE parameter types, sizes, validation maps, and tests ([#665](https://github.com/device-management-toolkit/go-wsman-messages/issues/665)) ([05e5dd4](https://github.com/device-management-toolkit/go-wsman-messages/commit/05e5dd4aa91f9e799cbef28532fcb59179d3ed11)) - -#### [2.38.4](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.38.3...v2.38.4) (2026-04-17) +#### [2.47.2](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.47.1...v2.47.2) (2026-06-03) Bug Fixes -* ack APF_CHANNEL_CLOSE so AMT can reclaim the channel slot ([#675](https://github.com/device-management-toolkit/go-wsman-messages/issues/675)) ([f4435ef](https://github.com/device-management-toolkit/go-wsman-messages/commit/f4435efc891c5f644f1be95118f5c79721503d5a)) +* Remove wiFiPortConfigurationService Put post-processes check ([#706](https://github.com/device-management-toolkit/go-wsman-messages/issues/706)) ([5276af1](https://github.com/device-management-toolkit/go-wsman-messages/commit/5276af138bd79737bf416f5a92b9678f236c0d27)) -#### [2.38.3](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.38.2...v2.38.3) (2026-04-17) +#### [2.47.1](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.47.0...v2.47.1) (2026-06-03) Bug Fixes -* ensure proper channel is being closed and adjusted ([bc8cfbf](https://github.com/device-management-toolkit/go-wsman-messages/commit/bc8cfbf772baf858044da48f272c8f76121b323e)) -* ensure proper channel is being closed and adjusted ([#674](https://github.com/device-management-toolkit/go-wsman-messages/issues/674)) ([18b1a72](https://github.com/device-management-toolkit/go-wsman-messages/commit/18b1a72e9f320b5b33f5f6fbab606c94c2ecdae1)) +* Remove omitempty from UEFIWiFiProfileShareEnabled ([#705](https://github.com/device-management-toolkit/go-wsman-messages/issues/705)) ([b5e72ad](https://github.com/device-management-toolkit/go-wsman-messages/commit/b5e72ad02166c39c249e937f8d682e6d826c0544)) -#### [2.38.2](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.38.1...v2.38.2) (2026-04-16) +#### [2.47.0](https://github.com/device-management-toolkit/go-wsman-messages/compare/v2.46.1...v2.47.0) (2026-06-03) -Bug Fixes +Features -* apf: event-driven response completion and window adjust replies ([#673](https://github.com/device-management-toolkit/go-wsman-messages/issues/673)) ([6ce79a9](https://github.com/device-management-toolkit/go-wsman-messages/commit/6ce79a9d4ea6c9fe9e8bd410e38095788a710df1)) +* add update wifi profile wsman adapter ([#686](https://github.com/device-management-toolkit/go-wsman-messages/issues/686)) ([3fb0776](https://github.com/device-management-toolkit/go-wsman-messages/commit/3fb07769fe6e52b1c24696a98e027d8d35350226)) ### WSMAN Messages -#### [6.0.2](https://github.com/device-management-toolkit/wsman-messages/compare/v6.0.1...v6.0.2) (2026-05-20) +#### [6.0.3](https://github.com/device-management-toolkit/wsman-messages/compare/v6.0.2...v6.0.3) (2026-06-03) ### MPS Router -#### [2.5.10](https://github.com/device-management-toolkit/mps-router/compare/v2.5.9...v2.5.10) (2026-05-20) \ No newline at end of file +#### [2.5.11](https://github.com/device-management-toolkit/mps-router/compare/v2.5.10...v2.5.11) (2026-06-03) \ No newline at end of file diff --git a/mkdocs.yml b/mkdocs.yml index 1361a4dfa..1947c0ae0 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -1,10 +1,10 @@ # Project information site_name: "Device Management Toolkit" site_url: "https://device-management-toolkit.github.io/docs/" -repo_url: "https://github.com/device-management-toolkit/cloud-deployment" -repo_name: "device-management-toolkit/cloud-deployment" +repo_url: "https://github.com/device-management-toolkit/deployment" +repo_name: "device-management-toolkit/deployment" copyright: "Copyright © 2021 Intel Corporation" -site_dir: site/2.34 +site_dir: site/2.35 # Configuration theme: name: "material" @@ -250,19 +250,19 @@ extra: - rapid - dev repoVersion: - release_name: "April 2026" + release_name: "May 2026" mpsAPI: 2.26.0 rpsAPI: 2.31.3 - oamtct: 2.34.0 - mps: 2.26.6 - rps: 2.36.4 - mps-router: 2.5.10 - rpc_go: 2.50.6 - webui: 3.57.7 + oamtct: 2.35.0 + mps: 2.26.7 + rps: 2.36.5 + mps-router: 2.5.11 + rpc_go: 2.50.8 + webui: 3.57.10 rpc_c: 2.0.0 - ui_toolkit: 3.3.15 - ui_toolkit_react: 5.0.4 - ui_toolkit_angular: 11.1.4 + ui_toolkit: 3.3.16 + ui_toolkit_react: 5.0.5 + ui_toolkit_angular: 11.1.5 analytics: provider: google property: "G-00QEDJW2TS" diff --git a/site/index.html b/site/index.html index f07df723e..141043581 100644 --- a/site/index.html +++ b/site/index.html @@ -3,7 +3,7 @@ Redirecting diff --git a/site/versions.json b/site/versions.json index 8e6d9570d..3609c4785 100644 --- a/site/versions.json +++ b/site/versions.json @@ -1,5 +1,6 @@ [ - {"version": "2.34", "title": "2.34 (Apr 26)", "aliases": ["rapid"]}, + {"version": "2.35", "title": "2.35 (May 26)", "aliases": ["rapid"]}, + {"version": "2.34", "title": "2.34 (Apr 26)", "aliases": []}, {"version": "2.33", "title": "2.33 (Mar 26)", "aliases": []}, {"version": "2.32", "title": "2.32 (Jan 26)", "aliases": []}, {"version": "2.31", "title": "2.31 (Dec 25)", "aliases": []},