Skip to content

Releases: PowerShell/vscode-powershell

v2023.11.0-preview

08 Nov 03:17
Compare
Choose a tag to compare
v2023.11.0-preview Pre-release
Pre-release

v2023.11.0-preview

Tuesday, November 07, 2023

vscode-powershell

Just dependencies.

PowerShellEditorServices v3.14.0

v2023.8.0

11 Oct 19:38
Compare
Choose a tag to compare

v2023.8.0

Wednesday, October 11, 2023

This one took a while! As always, these changes were available in the pre-release channel
which went through six versions to get us to today's release.

The cwd setting now supports ~ for home directory, relative paths, and named workspace
folders. The additionalPowerShellExes setting also now supports ~, checks for missing
extensions if necessary, and both settings smartly strip surrounding quotes from the
user-supplied value. These two settings are now far more user-friendly.

Thanks to efforts across the team, we are shipping the extension with the latest and
greatest PSReadLine, v2.3.4!

The extension commands AKA $psEditor API was reworked and no longer mangles path casing.
It also now exposes the CloseFile and SaveFile methods, and supports multi-root
workspaces.

A new setting integratedConsole.startLocation was added to control the Extension
Terminal's starting position. Thanks @krishankanumuri!

To wrap things up, another crash when $ErrorActionPreference = "stop" was resolved. A
race condition for the language status item's name and icon was fixed. Our telemetry went
down after a package upgrade which required a cross-team effort to resolve (it's now also
cleaned up to send just what we're using). The DSC breakpoints capability now works as
intended without causing module load errors or emitting "sticky" progress information. A
bug when the log level was set to None broke the server was fixed. Our server's major
dependency, OmniSharp's csharp-language-server-protocol, was updated to v0.19.9 which
means we can now use the current LSP spec v3.17. We had to work with the project to
resolve a serialization regression. Finally, a lot of various build improvements were
made.

Please note the change in our versioning schema: the middle version number no longer
corresponds to the month, but is simply incremented. Even versions are stable, and odd
versions are pre-release, with the latter purposefully being versioned higher than the
former in order to keep both channels available in the Visual Studio Code marketplace.

Thanks to all the many community contributors whose efforts make releases such as these
possible!

vscode-powershell

PowerShellEditorServices v3.13.0

v2023.9.5-preview

10 Oct 23:27
Compare
Choose a tag to compare
v2023.9.5-preview Pre-release
Pre-release

v2023.9.5-preview

Tuesday, October 10, 2023

vscode-powershell

PowerShellEditorServices v3.13.0

v2023.9.4-preview

29 Sep 21:58
Compare
Choose a tag to compare
v2023.9.4-preview Pre-release
Pre-release

v2023.9.4-preview

Friday, September 29, 2023

vscode-powershell

PowerShellEditorServices v3.12.0

Just updating the client above.

v2023.9.3-preview

28 Sep 22:06
Compare
Choose a tag to compare
v2023.9.3-preview Pre-release
Pre-release

v2023.9.3-preview

Thursday, September 28, 2023

vscode-powershell

PowerShellEditorServices v3.12.0

v2023.9.2-preview

13 Sep 23:56
Compare
Choose a tag to compare
v2023.9.2-preview Pre-release
Pre-release

v2023.9.2-preview

Wednesday, September 13, 2023

vscode-powershell

PowerShellEditorServices v3.11.0

v2023.9.1-preview

25 Aug 21:43
Compare
Choose a tag to compare
v2023.9.1-preview Pre-release
Pre-release

v2023.9.1-preview

Friday, August 25, 2023

vscode-powershell

PowerShellEditorServices v3.10.0

v2023.9.0-preview

10 Aug 21:38
Compare
Choose a tag to compare
v2023.9.0-preview Pre-release
Pre-release

v2023.9.0-preview

Wednesday, August 09, 2023

vscode-powershell

PowerShellEditorServices v3.9.0

v2023.6.0

06 Jun 20:13
Compare
Choose a tag to compare

v2023.6.0

Tuesday, June 06, 2023

This release focused on fixing the "disappearing output" bug present in PowerShell 5.1,
where an old bug with the Out-Default cmdlet's TranscribeOnly flag could cause the
Extension Terminal to stop displaying output. While the root cause in the cmdlet is fixed
upstream, that fix is only in PowerShell Core, and not backported to Windows PowerShell.
We were able to workaround the bug with a very careful use of reflection to reset the
flag's value at the appropriate times (see the three takes it took to get this right).

We also refactored the client's startup logic so that it should be impossible to create a
ghost Extension Terminal, and the error handling and logging was given a thorough cleanup.
Finally, two noisy bugs were fixed: when completions are canceled the useless error
message is no longer produced, and when the DSC module is only loaded in one attempt
instead of repeatedly.

Please enjoy these bugfixes! We sure enjoy making the extension more stable.

Don't forget to catch Andy's talk, "PowerShell Extension for VS Code Deep Dive" at
PSConfEU on Thursday, 22 June 2023!

vscode-powershell

PowerShellEditorServices v3.8.7

v2023.5.4-preview

31 May 18:30
Compare
Choose a tag to compare
v2023.5.4-preview Pre-release
Pre-release

v2023.5.4-preview

Tuesday, May 30, 2023

vscode-powershell

No changes, just pulling in PSES.

PowerShellEditorServices v3.8.7