Monday, November 28, 2022
HomePowershellPowerShell 7.3 Common Availability - PowerShell Group

PowerShell 7.3 Common Availability – PowerShell Group


We’re proud to announce the final availability of PowerShell 7.3!
PowerShell 7.3 is constructed on high of .NET 7 and as a non-LTS (Lengthy Time period Assist) launch can be supported for 18 months.
PowerShell 7.2 remains to be the present LTS (3-year supported) launch of PowerShell.

How do I get it?

Since PowerShell 7 is supported on Home windows, Linux, and macOS, there are a number of methods to get it.
In the event you had put in the earlier PowerShell 7 steady launch (7.2) by way of the Home windows Retailer,
you’ll be mechanically up to date to 7.3 GA.
Nonetheless, in case you put in the MSI and selected to be up to date by way of Microsoft Replace, since 7.2 is a LTS launch,
you’ll not be mechanically upgraded to 7.3 and must be manually put in.

What’s new?

You’ll be able to see a video of demos I introduced at this yr’s PSConfEU minicon.
It covers among the main modifications together with new options and vital bug fixes.
Numerous the work introduced have been contributions fromm the group!

Identified points

We discovered a final minute subject that ought to not have an effect on most customers that we are going to repair in an anticipated 7.3.1 launch in December.
On account of a problem with our framework dependent package deal to be included with the .NET SDK Docker photographs,
the .NET 7 GA SDK picture will nonetheless have PowerShell 7.3-rc.1 included.
This should have no useful impression to customers and we anticipate to replace the picture with PowerShell 7.3 GA in December.

Concentrate on the shell

The most important theme for this launch is specializing in making PowerShell 7 an important shell setting.
Right here, “native command” means an executable that’s not a PowerShell cmdlet or perform.

Enchancment to native command argument passing

Home windows and Linux/macOS have elementary variations in how native command arguments are dealt with particularly when quotes are concerned.
We added a brand new characteristic $PSNativeCommandArgumentPassing
to manage how PowerShell passes arguments to native instructions.
The default conduct for Home windows and Linux/macOS ought to work as most customers anticipate of their respective environments.

One other space to make native instructions work extra like cmdlets is error dealing with.
In contrast to cmdlets, native instructions use their exit code to convey success or failure.

Consistency in error dealing with for native instructions

Though stderr is commonly used for error messages,
additionally it is used for progress, data, warnings, and many others. as a result of native instructions don’t have the wealthy streams that PowerShell cmdlets have.
Though a non-zero exit code does NOT at all times point out an error, the conference for native instructions is {that a} non-zero exit code sometimes signifies an error.

A brand new characteristic $PSNativeCommandUseErrorActionPreference
means that you can have PowerShell deal with a non-zero exit code as an error.
This implies that you would be able to set $ErrorActionPreference
to Cease and have PowerShell cease execution whether or not a cmdlet had an error or a local command had a non-zero exit code.

This simplifies scripts that beforehand must examine $LASTEXITCODE
after execution of a local command or wrap it in a helper perform.

What’s subsequent?

PowerShell 7.4 can be our subsequent LTS launch and anticipated to be constructed on .NET 8 for subsequent yr.
We’ll have a separate weblog publish early subsequent yr to debate the investments of the PowerShell/OpenSSH workforce for 2023.
We respect all of the efforts of the group, each people and working group members,
and stay up for your continued suggestions and contributions!

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Most Popular

Recent Comments