RelNotes: Preview Runtime 154, Runtime 153

microsoft-edge/toc.yml

@@ -1534,7 +1534,10 @@
                 - name: Release notes for the WebView2 Runtime
                   href: ./webview2/release-notes/runtime/index.md
 
-                - name: Preview Runtime 153.0.4234.6 (Aug. 28, 2026)
+                - name: Preview Runtime 154.0.4255.0 (Sep. 3, 2026)
+                  href: ./webview2/release-notes/runtime/154.md
+
+                - name: Runtime nnn.n.nnnn.nn (Mmm. dd, yyyy)
                   href: ./webview2/release-notes/runtime/153.md
 
                 - name: Runtime 152.0.4191.53 (Aug. 28, 2026)
@@ -1776,6 +1779,12 @@
                 - name: Release notes for WebView2 SDKs
                   href: ./webview2/release-notes/sdk/index.md
 
+                - name: SDK 1.0.4255-prerelease, for Runtime 154 (Sep. 3, 2026)
+                  href: ./webview2/release-notes/sdk/1-0-4255-prerelease.md
+
+                - name: SDK n.n.nnnn.nn, for Runtime nnn (Mmm. dd, yyyy)
+                  href: ./webview2/release-notes/sdk/n-n-nnnn-nn.md
+
                 - name: SDK 1.0.4191.47, for Runtime 152 (Aug. 28, 2026)
                   href: ./webview2/release-notes/sdk/1-0-4191-47.md
 
@@ -2401,9 +2410,6 @@
 # -----------------------------------------------------------------------------
         - name: Test and automation for WebView2 apps
           items:
-            - name: Test upcoming APIs and features
-              href: ./webview2/how-to/set-preview-channel.md
-
             - name: Use the Chrome DevTools Protocol (CDP) in WebView2 apps
               href: ./webview2/how-to/chromium-devtools-protocol.md
               displayName: chrome developer protocol  # catch mis-expansion
@@ -2414,12 +2420,17 @@
             - name: Automate and test WebView2 apps with Microsoft Edge WebDriver
               href: ./webview2/how-to/webdriver.md
 
-            - name: Prerelease testing using preview channels
-              href: ./webview2/how-to/prerelease-testing.md
+            - name: Prerelease testing using preview channels of Microsoft Edge
+              items:
+                - name: Prerelease testing using preview channels of Microsoft Edge  # short article
+                  href: ./webview2/how-to/prerelease-testing.md
+
+                - name: Switch to a preview channel to test upcoming APIs and features  # long article
+                  href: ./webview2/how-to/set-preview-channel.md
 
-            - name: Self-host by deploying preview channels
-              href: ./webview2/how-to/self-hosting.md
-              displayName: self-hosting
+                - name: Self-host by deploying preview channels
+                  href: ./webview2/how-to/self-hosting.md
+                  displayName: self-hosting
 # -----------------------------------------------------------------------------
         - name: Debug WebView2 apps
           items:

microsoft-edge/webview2/concepts/developer-guide.md

@@ -52,7 +52,7 @@ When using the Evergreen WebView2 Runtime, run forward-compatibility tests by us
 
 Because the Evergreen Runtime updates automatically, you should regularly run compatibility tests to ensure that your WebView2 app will continue to work as expected on the new Runtime version.  This can be done by testing your web content in the WebView2 control against the Microsoft Edge preview channels.
 
-Follow the guidance in [Prerelease testing using preview channels](../how-to/prerelease-testing.md) and [Self-host by deploying preview channels](../how-to/self-hosting.md).
+Follow the guidance in [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md) and [Self-host by deploying preview channels](../how-to/self-hosting.md).
 
 
 <!-- ------------------------------ -->
@@ -146,7 +146,7 @@ Follow the guidance in [Develop secure WebView2 apps](./security.md).
    * [The Fixed Version runtime distribution mode](./distribution.md#the-fixed-version-runtime-distribution-mode) in _Distribute your app and the WebView2 Runtime_.
    * [Handle Evergreen WebView2 Runtime updates](./distribution.md#handle-evergreen-webview2-runtime-updates) in _Distribute your app and the WebView2 Runtime_.
 * [Develop secure WebView2 apps](./security.md)<!-- bucket 7 -->
-* [Prerelease testing using preview channels](../how-to/prerelease-testing.md)<!-- bucket 8 bottom -->
+* [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md)<!-- bucket 8 bottom -->
 * [Self-host by deploying preview channels](../how-to/self-hosting.md)<!-- bucket 8 very bottom -->
 * [Manage user data folders](./user-data-folder.md)<!-- bucket 11 -->
 

microsoft-edge/webview2/concepts/distribution.md

@@ -33,7 +33,7 @@ During development and testing, a WebView2 app can use either option as the back
 
 * The WebView2 Runtime.  The Runtime generally provides the same web platform capabilities and update release cadence as the Stable channel of the Microsoft Edge browser; see [Microsoft Edge release schedule](/deployedge/microsoft-edge-release-schedule).  Use the WebView2 Runtime in a production environment or to develop and test against the web platform that your users have today.
 
-* A preview (Insider) Microsoft Edge browser channel.  These Microsoft Edge preview channels are Beta, Dev, and Canary.  Use this approach to test your app for forward-compatibility, so that you know if a breaking change is coming that will require updating your app.  See [Test upcoming APIs and features](../how-to/set-preview-channel.md).
+* A preview (Insider) Microsoft Edge browser channel.  These Microsoft Edge preview channels are Beta, Dev, and Canary.  Use this approach to test your app for forward-compatibility, so that you know if a breaking change is coming that will require updating your app.  See [Switch to a preview channel to test upcoming APIs and features](../how-to/set-preview-channel.md).
 
 A production release of a WebView2 app can only use the WebView2 Runtime as the backing web platform, not Microsoft Edge.
 
@@ -224,7 +224,7 @@ To use the new version of the WebView2 Runtime, you need to either release all r
 
 In the Evergreen distribution mode, the WebView2 Runtime is automatically kept up to date on the client to provide the latest features and security fixes.  If you use Evergreen distribution, to ensure that your WebView2 app stays compatible with the web, you should set up testing infrastructure.
 
-For best practices about how to test your app for forward-compatibility, see [Prerelease testing using preview channels](../how-to/prerelease-testing.md) and [Self-host by deploying preview channels](../how-to/self-hosting.md).
+For best practices about how to test your app for forward-compatibility, see [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md) and [Self-host by deploying preview channels](../how-to/self-hosting.md).
 
 
 <!-- ------------------------------ -->
@@ -360,8 +360,8 @@ Example managed app folder structure:
    * [Feature-detecting to test whether the installed Runtime supports recently added APIs](./versioning.md#feature-detecting-to-test-whether-the-installed-runtime-supports-recently-added-apis) in _Prerelease and Release SDKs for WebView2_.
 * [Evergreen vs. fixed version of the WebView2 Runtime](./evergreen-vs-fixed-version.md)<!-- toc bucket 6 leaf 3 -->
 * [Windows Server Update Services (WSUS)](./enterprise.md#windows-server-update-services-wsus) in _Enterprise management of WebView2 Runtimes_.<!-- toc bucket 6 leaf 4 -->
-* [Test upcoming APIs and features](../how-to/set-preview-channel.md)<!-- toc bucket 8 top -->
-* [Prerelease testing using preview channels](../how-to/prerelease-testing.md)<!-- toc bucket 8 bottom -->
+* [Switch to a preview channel to test upcoming APIs and features](../how-to/set-preview-channel.md)<!-- toc bucket 8 top -->
+* [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md)<!-- toc bucket 8 bottom -->
 * [Self-host by deploying preview channels](../how-to/self-hosting.md)<!-- toc bucket 8 very bottom -->
 * [Distribute a WebView2 app as a single executable file](../how-to/static.md) - statically linking the WebView2 loader library.
 

microsoft-edge/webview2/concepts/overview-features-apis.md

@@ -3681,8 +3681,8 @@ Runtime selection supports prerelease testing and self-hosting.  When creating a
 * To specify which browser preview channels are searched for, use the `CoreWebView2EnvironmentOptions.ReleaseChannels` property.
 
 See also:
-* [Test upcoming APIs and features](../how-to/set-preview-channel.md)
-* [Prerelease testing using preview channels](../how-to/prerelease-testing.md)
+* [Switch to a preview channel to test upcoming APIs and features](../how-to/set-preview-channel.md)
+* [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md)
 * [Self-host by deploying preview channels](../how-to/self-hosting.md)
 
 ##### [.NET/C#](#tab/dotnetcsharp)

microsoft-edge/webview2/concepts/security.md

@@ -112,17 +112,17 @@ When the host process is running elevated:
    * [Setting browser flags programmatically through code](./webview-features-flags.md#setting-browser-flags-programmatically-through-code) in _WebView2 browser flags_.
 
 * `HKEY_CURRENT_USER` (`HKCU`) policy overrides are ignored.  See:
-   * [Switching the channel search order (recommended)](../how-to/set-preview-channel.md#switching-the-channel-search-order-recommended) in _Test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKCU`.
-   * [How to use `ChannelSearchKind` to ensure that a particular channel is used](../how-to/set-preview-channel.md#how-to-use-channelsearchkind-to-ensure-that-a-particular-channel-is-used) in _Test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKCU`.
-   * [Setting the browser executable folder (for local testing)](../how-to/set-preview-channel.md#setting-the-browser-executable-folder-for-local-testing) in _Test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKCU`.
+   * [Switching the channel search order (recommended)](../how-to/set-preview-channel.md#switching-the-channel-search-order-recommended) in _Switch to a preview channel to test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKCU`.
+   * [How to use `ChannelSearchKind` to ensure that a particular channel is used](../how-to/set-preview-channel.md#how-to-use-channelsearchkind-to-ensure-that-a-particular-channel-is-used) in _Switch to a preview channel to test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKCU`.
+   * [Setting the browser executable folder (for local testing)](../how-to/set-preview-channel.md#setting-the-browser-executable-folder-for-local-testing) in _Switch to a preview channel to test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKCU`.
    * [Debug WebView2 apps with Visual Studio Code](../how-to/debug-visual-studio-code.md) - Find `HKEY_CURRENT_USER`.
 
 * `AdditionalBrowserArguments` registry overrides that are under `HKCU` are ignored.
 
 * `HKEY_LOCAL_MACHINE` (`HKLM`) policy overrides are honored.  See:
-   * [Switching the channel search order (recommended)](../how-to/set-preview-channel.md#switching-the-channel-search-order-recommended) in _Test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKLM`.
-   * [How to use `ChannelSearchKind` to ensure that a particular channel is used](../how-to/set-preview-channel.md#how-to-use-channelsearchkind-to-ensure-that-a-particular-channel-is-used) in _Test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKLM`.
-   * [Setting the browser executable folder (for local testing)](../how-to/set-preview-channel.md#setting-the-browser-executable-folder-for-local-testing) in _Test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKLM`.
+   * [Switching the channel search order (recommended)](../how-to/set-preview-channel.md#switching-the-channel-search-order-recommended) in _Switch to a preview channel to test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKLM`.
+   * [How to use `ChannelSearchKind` to ensure that a particular channel is used](../how-to/set-preview-channel.md#how-to-use-channelsearchkind-to-ensure-that-a-particular-channel-is-used) in _Switch to a preview channel to test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKLM`.
+   * [Setting the browser executable folder (for local testing)](../how-to/set-preview-channel.md#setting-the-browser-executable-folder-for-local-testing) in _Switch to a preview channel to test upcoming APIs and features_ - Select the **Registry key** tab, and then Find `HKLM`.
 
 Non-elevated WebView2 apps honor all of the supported override mechanisms.
 

microsoft-edge/webview2/concepts/versioning.md

@@ -63,11 +63,11 @@ The Prerelease SDK package is a superset of the Release SDK package.  A Prerelea
 
 Preview channels of Microsoft Edge provide the implementations of Experimental WebView2 APIs and of Stable APIs.  The Experimental APIs are subject to change based on feedback.  Avoid using a Prerelease SDK package to build production apps.
 
-For information about temporarily pointing your app to a preview channel instead of defaulting to the WebView2 Runtime, see [Test upcoming APIs and features](../how-to/set-preview-channel.md).
+For information about temporarily pointing your app to a preview channel instead of defaulting to the WebView2 Runtime, see [Switch to a preview channel to test upcoming APIs and features](../how-to/set-preview-channel.md).
 
 See also:
 * [Evergreen vs. fixed version of the WebView2 Runtime](./evergreen-vs-fixed-version.md)
-* [Prerelease testing using preview channels](../how-to/prerelease-testing.md)
+* [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md)
 * [Self-host by deploying preview channels](../how-to/self-hosting.md)
 
 
@@ -212,8 +212,8 @@ If your code determines that an API is unavailable in the client's installed Web
 * [WebView2 deployment samples](../samples/deployment-samples.md)<!-- link not in article --><!-- bucket 2 -->
 * [Evergreen vs. fixed version of the WebView2 Runtime](./evergreen-vs-fixed-version.md)<!-- bucket 6 -->
 * [Distribute your app and the WebView2 Runtime](./distribution.md)<!-- bucket 6 -->
-* [Test upcoming APIs and features](../how-to/set-preview-channel.md)<!-- bucket 8 top -->
-* [Prerelease testing using preview channels](../how-to/prerelease-testing.md)<!-- bucket 8 bottom -->
+* [Switch to a preview channel to test upcoming APIs and features](../how-to/set-preview-channel.md)<!-- bucket 8 top -->
+* [Prerelease testing using preview channels of Microsoft Edge](../how-to/prerelease-testing.md)<!-- bucket 8 bottom -->
 * [Self-host by deploying preview channels](../how-to/self-hosting.md)<!-- bucket 8 very bottom -->
 * [Phases of adding APIs](../release-notes/about.md#phases-of-adding-apis) in _About Release notes for the WebView2 SDK_.<!-- bucket 12 -->
 * [Release notes for WebView2](../release-notes/index.md)<!-- bucket 12 -->

microsoft-edge/webview2/how-to/prerelease-testing.md

@@ -1,5 +1,5 @@
 ---
-title: Prerelease testing using preview channels
+title: Prerelease testing using preview channels of Microsoft Edge
 description: How to test your WebView2 app by using the preview channels of Microsoft Edge (Edge Canary, Edge Dev, or Edge Beta) to find issues that will affect your particular WebView2 app, before WebView2 changes reach  the Evergreen WebView2 Runtime.
 author: MSEdgeTeam
 ms.author: msedgedevrel
@@ -8,10 +8,14 @@ ms.service: microsoft-edge
 ms.subservice: webview
 ms.date: 04/22/2024
 ---
-# Prerelease testing using preview channels
+# Prerelease testing using preview channels of Microsoft Edge
+<!-- short article -->
 
 _Prerelease testing_ means testing your WebView2 app by using the preview channels of Microsoft Edge to find issues that will affect your particular WebView2 app, before any changes ship in the Stable Evergreen WebView2 Runtime.  This helps catch any bugs before they degrade the app experience for end users.
 
+See also:
+* [Switch to a preview channel to test upcoming APIs and features](./set-preview-channel.md)<!-- todo: explicitly relate/ compare/ contrast the two articles -->
+
 Conduct both automated and manual testing:
 * For **automated testing**, do **prerelease testing**, which means testing with a WebView2 Preview Runtime.  Covered by the present article.
 * For **manual testing**, use **self-hosting**, which means deploying a WebView2 Preview Runtime with your app, to use daily by your team.  See [Self-host by deploying preview channels](./self-hosting.md).
@@ -38,12 +42,12 @@ To do automated testing:
 
 1. **Set the preview channel for your app.**
 
-   You can set the preview channel by using `ChannelSearchKind`, so that your WebView2 app uses the least-stable channel (Canary, then Dev).  To do this, see [Switching the channel search order (recommended)](./set-preview-channel.md#switching-the-channel-search-order-recommended) in _Test upcoming APIs and features_.
+   You can set the preview channel by using `ChannelSearchKind`, so that your WebView2 app uses the least-stable channel (Canary, then Dev).  To do this, see [Switching the channel search order (recommended)](./set-preview-channel.md#switching-the-channel-search-order-recommended) in _Switch to a preview channel to test upcoming APIs and features_.
 
 1. **Install or deploy the preview channel.**
 
    * If you choose to install preview channels manually, install them from the page [Become a Microsoft Edge Insider](https://www.microsoft.com/edge/download/insider).
-   * If you instead choose to deploy preview channels to devices, see [How to deploy preview channels](./set-preview-channel.md#how-to-deploy-preview-channels) in _Test upcoming APIs and features_.
+   * If you instead choose to deploy preview channels to devices, see [How to deploy preview channels](./set-preview-channel.md#how-to-deploy-preview-channels) in _Switch to a preview channel to test upcoming APIs and features_.
 
 1. **Conduct automated testing on your app running against the preview channels.**
 
@@ -60,7 +64,7 @@ Upon finding issues, you can report them via the [Microsoft Edge / WebView2Feedb
 ## See also
 
 * [Self-host by deploying preview channels](./self-hosting.md)
-* [Test upcoming APIs and features](./set-preview-channel.md)
+* [Switch to a preview channel to test upcoming APIs and features](./set-preview-channel.md)
 * [Automate and test WebView2 apps with Microsoft Edge WebDriver](./webdriver.md)
 * [Site compatibility-impacting changes coming to Microsoft Edge](../../web-platform/site-impacting-changes.md)
 * [WebView2 feedback repo](https://github.com/MicrosoftEdge/WebView2Feedback)