Michael Hoffman (mikehoffms) · Oct 6, 2026 · Oct 6, 2026 · Oct 6, 2026
diff --git a/microsoft-edge/web-platform/prompt-api.md b/microsoft-edge/web-platform/prompt-api.md
@@ -162,7 +162,7 @@ By default, the Prompt API uses the Phi-4-mini model.  To use Aion-1.0-Instruct
 <!-- ------------------------------ -->
 #### Disclaimer
 
-The Aion-1.0-Instruct model is made available in Microsoft Edge 150.0.4070 for early developer testing and feedback.  In addition to the Responsible AI considerations listed above, note that, given its prerelease state, model behaviors and capabilities are subject to change.
+The Aion-1.0-Instruct model is available in Microsoft Edge for early developer testing and feedback.  In addition to the Responsible AI considerations listed above, note that, given its prerelease state, model behaviors and capabilities are subject to change.
 
 
 <!-- ------------------------------ -->

diff --git a/microsoft-edge/web-platform/site-impacting-changes.md b/microsoft-edge/web-platform/site-impacting-changes.md
@@ -35,12 +35,18 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
 | Change | Release | Description |
 | --- | --- | --- |
 | Insecure downloads over HTTP | Future release (TBD) | When a user tries to download potentially dangerous content from an HTTP site, the user will receive a UI warning, such as "Insecure download blocked."  The user will still have an option to proceed and download the item.  Admins can use the `InsecureContentAllowedForUrls` policy to specify HTTP sites for which the warning will be suppressed.  Admins can use the `InsecureDownloadWarnings` feature flag to test the impact of this upcoming feature. |
-| Deprecation of XSLT | Future release (TBD) | XSLT support represents a disproportionate attack surface, and the Chromium project which Microsoft Edge is based on has announced plans to disable and ultimately remove XSLT in a future release. See [Removing XSLT for a more secure browser](https://developer.chrome.com/docs/web-platform/deprecating-xslt). As a result, you should treat reliance on client‑side XSLT as technical debt and plan migration accordingly. Microsoft Edge version 147 introduces the XSLTEnabled feature policy to support testing and transition scenarios while the Chromium project works toward deprecating and removing XSLT support. We encourage organizations to proactively test setting `XSLTEnabled = Disabled` to identify application dependencies and remediation requirements ahead of any future default changes or removal of the feature. |
+| Deprecation of XSLT | v159 (v157 in Edge Canary, Dev, and Beta) | XSLT support represents a disproportionate attack surface, and the Chromium project which Microsoft Edge is based on has announced plans to disable and ultimately remove XSLT in a future release. See [Removing XSLT for a more secure browser](https://developer.chrome.com/docs/web-platform/deprecating-xslt). As a result, you should treat reliance on client‑side XSLT as technical debt and plan migration accordingly. Microsoft Edge version 147 introduces the XSLTEnabled feature policy to support testing and transition scenarios while the Chromium project works toward deprecating and removing XSLT support. We encourage organizations to proactively test setting `XSLTEnabled = Disabled` to identify application dependencies and remediation requirements ahead of any future default changes or removal of the feature. |
 | Remove `_current` link target | v153 | The non-standard `_current` link target, which is used to specify that a link should open in the current browsing context, is removed.  See [Removed `_current` link target](./release-notes/153.md#removed-_current-link-target) in _Microsoft Edge 153 web platform release notes (Sep. 10, 2026)_. |
 | Deprecate unload event | v152-v155 | Edge 152 will introduce the new `unload` Permission-Policy, to allow creating unload event listeners.  The default value is initially `allow`, but between Edge 152 and Edge 155, the default value will gradually be migrated to `deny`, such that unload handlers stop firing on pages, unless a page explicitly opts in to re-enable them.  To explicitly enable unload event handlers, use the `allow` value.  <br/>Edge 152: Unload handlers will stop firing by default for 60% of page loads, unless the site explicitly enables unload handlers via the `unload` Permission-Policy.  <br/>Edge 154: Increases to 80% of page loads.  <br/>Edge 155: Increases to 100% of page loads.  <br/>This change is happening in the Chromium project, on which Microsoft Edge is based.  See [Planned deprecation of the unload event](./release-notes/152.md#planned-deprecation-of-the-unload-event) in _Microsoft Edge 152 web platform release notes (Aug. 27, 2026)_, and [Intent to Deprecate: Deprecate unload event](https://groups.google.com/a/chromium.org/g/blink-dev/c/dvusqw9-IhI/m/SBkm_u1RAQAJ). |
 | Remove inline XSLT for production of SVG | v147 | Support for using XSLT stylesheets to transform XML data into SVG files has been removed.  See [Remove inline XSLT for production of SVG](./release-notes/147.md#remove-inline-xslt-for-production-of-svg) in _Microsoft Edge 147 web platform release notes (Apr. 2026)_. |
 | JPEG or PNG embedded in BMP | v145 | Support for embedding JPEG or PNG image data in a Bitmap image format is nonstandard, and has been removed.  See [Remove support for Bitmap extension to embed JPEG or PNG](./release-notes/145.md#remove-support-for-bitmap-extension-to-embed-jpeg-or-png) in _Microsoft Edge 145 web platform release notes (Feb. 2026)_. |
 | Externally loaded entities in XML parsing | v144 | Synchronous fetching of external XML entities/DTDs, which are then used when parsing under specific circumstances, has been removed. See [Externally loaded entities in XML parsing](./release-notes/144.md#externally-loaded-entities-in-xml-parsing), in _Microsoft Edge 144 web platform release notes (Jan. 2025)_. |
+
+
+##### [Earlier versions](#tab/earlier)
+
+| Change | Release | Description |
+| --- | --- | --- |
 | Deprecate `Intl.Locale` getters | v143 | The accessor properties of the `Intl.Locale` object are now deprecated, in favor of the corresponding functions, per specification. See [Deprecate `Intl.Locale` getters](./release-notes/143.md#deprecate-intllocale-getters), in _Microsoft Edge 143 web platform release notes (Dec. 2025)_. |
 | Mobile and desktop parity for `<select>` elements | v142 | The appearance of `<select>` HTML elements, when using the `multiple` and `size` attributes, is now consistent across mobile and desktop devices. See [Mobile and desktop parity for `<select>` elements](./release-notes/142.md#mobile-and-desktop-parity-for-select-elements), in _Microsoft Edge 142 web platform release notes (Oct. 2025)_. |
 | Remove special font size rules for `<h1>` | v140 | The special margin and font size rules for `<h1>` elements, when nested in `<article>`, `<aside>`, `<nav>`, and `<section>` elements, are now removed, to improve accessibility. See [Removed special font size rules for `<h1>` within some elements](./release-notes/140.md#removed-special-font-size-rules-for-h1-within-some-elements) in _Microsoft Edge 140 web platform release notes (Sep. 2025)_. |
@@ -51,12 +57,6 @@ This table lists high-impact changes which the Microsoft Edge team is tracking c
 | Remove `navigator.xr.supportsSession` method | v135 | The deprecated `navigator.xr.supportsSession` property is removed from the WebXR API. See [Remove `navigator.xr.supportsSession` method](./release-notes/135.md#remove-navigatorxrsupportssession-method), in _Microsoft Edge 135 web platform release notes (Apr. 2025)_. |
 | Remove WebGPU limit `maxInterStageShaderComponents` | v135 | The `maxInterStageShaderComponents` limit is now removed. See [Remove WebGPU limit `maxInterStageShaderComponents`](./release-notes/135.md#remove-webgpu-limit-maxinterstageshadercomponents), in _Microsoft Edge 135 web platform release notes (Apr. 2025)_. |
 | Deprecate `-ms-high-contrast` and `-ms-high-contrast-adjust` | v134-v138 | The CSS `-ms-high-contrast` media query and the `-ms-high-contrast-adjust` property are being deprecated, in favor of the standard-based **forced colors** feature.  See [Deprecating support for -ms-high-contrast and -ms-high-contrast-adjust](https://blogs.windows.com/msedgedev/2024/04/29/deprecating-ms-high-contrast/). |
-
-
-##### [Earlier versions](#tab/earlier)
-
-| Change | Release | Description |
-| --- | --- | --- |
 | WebGPU `maxInterStageShaderComponents` limit | v133 | The WebGPU `maxInterStageShaderComponents` limit is being removed.  See [Deprecate WebGPU limit maxInterStageShaderComponents](./release-notes/133.md#deprecate-webgpu-limit-maxinterstageshadercomponents). |
 | `<link rel=prefetch>` five-minute rule | v133 | Previously, when a resource was prefetched by using `<link rel=prefetch>`, its cache semantics (specifically, `max-age` and `no-cache`) were ignored for the first use within 5 minutes, to avoid refetching.  Now, this special case has been removed, and normal HTTP cache semantics are used. See [Remove `<link rel=prefetch>` five-minute rule](./release-notes/133.md#remove-link-relprefetch-five-minute-rule). |
 | Deprecate `textprediction` attribute | v133 | Removes support for the `textprediction` HTML attribute, which is a nonstandard attribute that's used to enable or disable the browser-based Text Prediction feature for long-form text inputs.  Instead, use the standardized `writingsuggestions` attribute, which functions similarly to `textprediction`, but also applies to other writing-assistance features that browsers may provide.  Sites that explicitly set `textprediction` to `true` or `false` can instead set `writingsuggestions` to the same value.  For more information, see [Writing suggestions](https://html.spec.whatwg.org/multipage/interaction.html#writing-suggestions) in the HTML specification. |

diff --git a/microsoft-edge/web-platform/speech-recognition-api.md b/microsoft-edge/web-platform/speech-recognition-api.md
@@ -148,7 +148,7 @@ recognition.lang = "en-US";
 recognition.processLocally = true;
 ```
 
-As of Microsoft Edge 150.0.4076, the following input languages are supported for local speech recognition:
+The following input languages are supported for local speech recognition:
 * English (en-US)
 * German (de-DE)
 * Italian (it-IT)

diff --git a/microsoft-edge/web-platform/writing-assistance-apis.md b/microsoft-edge/web-platform/writing-assistance-apis.md
@@ -162,7 +162,7 @@ By default, the Writing Assistance APIs use the Phi-4-mini model.  To use Aion-1
 <!-- ------------------------------ -->
 #### Disclaimer
 
-The Aion-1.0-Instruct model is made available in Microsoft Edge 150.0.4070 for early developer testing and feedback.  In addition to the Responsible AI considerations listed above, note that, given its prerelease state, model behaviors and capabilities are subject to change.
+The Aion-1.0-Instruct model is available in Microsoft Edge for early developer testing and feedback.  In addition to the Responsible AI considerations listed above, note that, given its prerelease state, model behaviors and capabilities are subject to change.
 
 
 <!-- ------------------------------ -->

diff --git a/scripts/report-references-to-old-versions.js b/scripts/report-references-to-old-versions.js
@@ -48,8 +48,7 @@ const FILES_TO_IGNORE = [
   '../microsoft-edge/progressive-web-apps/whats-new/*.md',
 
   // WebView2
-  '../microsoft-edge/webview2/release-notes/index.md',
-  '../microsoft-edge/webview2/release-notes/archive.md',
+  '../microsoft-edge/webview2/release-notes/**/*.md',
 
   // Test and automation
   // -- No files to ignore yet --