From 0253eb76ca543a495e0f4e53a316f3476fb628dd Mon Sep 17 00:00:00 2001
From: Andy Jordan <2226434+andyleejordan@users.noreply.github.com>
Date: Wed, 8 Oct 2025 10:43:56 -0700
Subject: [PATCH] v2025.4.0: New stable release!

Now with screen reader support from PSReadLine 2.4.x
and arbitrary path mapping support in the debugger.
---
 CHANGELOG.md | 13 +++++++++++--
 package.json |  2 +-
 2 files changed, 12 insertions(+), 3 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index c7bd8f3455..6218f7246e 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,15 @@
 # PowerShell Extension Release History
 
+## v2025.4.0
+### Wednesday, October 08, 2025
+
+With PowerShell Editor Services [v4.4.0](https://github.com/PowerShell/PowerShellEditorServices/releases/tag/v4.4.0)!
+
+New stable release! Now with screen reader support from PSReadLine [2.4.4-beta4](https://github.com/PowerShell/PSReadLine/releases/tag/v2.4.4-beta4)
+and arbitrary path mapping support in the debugger.
+
+See more details at the GitHub Release for [v2025.4.0](https://github.com/PowerShell/vscode-powershell/releases/tag/v2025.4.0).
+
 ## v2025.5.0-preview
 ### Tuesday, September 09, 2025
 
@@ -257,7 +267,6 @@ being such fantastic users!
 
 #### [vscode-powershell](https://github.com/PowerShell/vscode-powershell)
 
-
 #### [PowerShellEditorServices](https://github.com/PowerShell/PowerShellEditorServices) v3.14.0
 
 - 🐛 📟 [vscode-powershell #4788](https://github.com/PowerShell/PowerShellEditorServices/pull/2091) - Run `SetInitialWorkingDirectoryAsync` before `LoadProfiles`.
@@ -1963,7 +1972,7 @@ This release also contains all changes listed in [v2021.8.1-preview](#v202181-pr
 below. Notably it fixes several major issues when debugging scripts that were caused by
 threading deadlocks in both PowerShell Editor Services and its library, [OmniSharp's C#
 Language Server Protocol][omnisharp] that we resolved by setting the compiler to treat
-[CA2007][] as an error. This allowed us to programmatically fix _every_ awaited task to
+[CA2007][] as an error. This allowed us to programmatically fix *every* awaited task to
 use `.ConfigureAwait(false)` and so avoid deadlocks caused by the introduction of new
 synchronization contexts in user code (such as the use of `System.Windows.Forms`). By
 fixing this through a compiler rule, we effectively prevent the issue from recurring.
diff --git a/package.json b/package.json
index 08f4e5be71..88677c6656 100644
--- a/package.json
+++ b/package.json
@@ -1,7 +1,7 @@
 {
   "name": "powershell",
   "displayName": "PowerShell",
-  "version": "2025.5.0",
+  "version": "2025.4.0",
   "preview": false,
   "publisher": "ms-vscode",
   "description": "Develop PowerShell modules, commands and scripts in Visual Studio Code!",