First, apologies getting this out so late into the yr.
We’ve been very busy and simply discovered the time to write down this replace.
Safety enhancements
We proceed to deal with safety as a high precedence and as points are found or reported,
we’ll proceed to prioritize these points over new characteristic growth.
Bug fixes and group PRs
We proceed to repair varied reported points, in addition to prioritizing the overview and merging of group pull requests.
Primarily based on group suggestions, we’re now utilizing a GitHub challenge to supply transparency
on which points and pull requests crew members are specializing in.
PowerShell 7.6
PowerShell 7.6 will probably be our newest Lengthy-Time period Servicing (LTS) launch.
We proceed to align with the .NET 10 launch cycle and help lifecycle.
There have already been 4 preview releases printed.
Transferring PowerShell content material folder out of MyDocuments
This has been a long-standing request from the group on account of computerized sync of MyDocuments folder and OneDrive.
Whereas some customers wish to leverage OneDrive for syncing throughout their techniques,
many different customers complain in regards to the efficiency affect on PowerShell module discovery when modules are saved within the OneDrive folder.
There was a earlier experimental characteristic PSModuleAutoLoadSkipOfflineFiles that’s now mainstream in PowerShell 7.5.
With this alteration, PowerShell skips modules that aren’t marked being out there regionally.
Nonetheless, this additionally led to confusion for customers who anticipated their modules to be out there once they weren’t on disk.
As any change here’s a breaking change, we’ve spent a number of time discussing one of the best ways to method this.
We’re near ending a proposal that we’ll publish to the PowerShell-RFC repository for
group suggestions when prepared.
We could have experimental characteristic out there throughout the 7.6 preview cycle for customers to check and supply suggestions on.
Observe that the PowerShell content material folder doesn’t simply include modules, but in addition the consumer’s PowerShell profile, scripts put in from PowerShell Gallery,
and up to date assist recordsdata.
Allow native instructions to combine with PowerShell extra simply
A standard ask from a number of of our Microsoft companions who’re constructing native instructions (Azure CLI, Winget) is to extra simply
combine options reminiscent of Suggestions Suppliers and Tab Completion the place they don’t must publish a separate module from their
utility.
We have now already printed a design proposal in our RFC repo and would welcome
any suggestions from the group.
One of many key necessities is that an utility’s set up and uninstall must be clear and never depart behind any artifacts in PowerShell.
Replace PATH surroundings variable for WinGet
At present, for those who use WinGet to put in a bundle, it won’t replace the PATH surroundings variable.
Which means newly put in purposes aren’t out there within the present PowerShell session.
This characteristic will probably be just like the one made in cmd.exe and solely apply to a selected purposes.
PowerShell 7 configuration as DSC v3 useful resource
As a part of our work to allow managing in style developer purposes’ settings,
we’re engaged on exposing pwsh as a DSC v3 useful resource.
It will permit customers to handle the settings of PowerShell 7 in a declarative method.
PowerShell Gallery
Vital behind-the-scenes work is going on emigrate the PowerShell Gallery from an Azure Cloud Providers basic utility
to 1 hosted on Azure Kubernetes Service (AKS).
It is a troublesome effort however, ideally, one which gained’t have an effect on consumer entry or efficiency.
EntraID server-side help
Concurrently, we’re engaged on help for EntraID authentication that
permits customers to make use of a managed determine to publish modules to the PowerShell Gallery as an alternative of an API key.
PSResourceGet
EntraID client-side help
Together with the adjustments needed on the PowerShell Gallery facet, corresponding adjustments are being made to PSResourceGet
to help EntraID authentication.
Full Micorosft Artifact Registry (MAR) help
We proceed to progress in the direction of Common Availability for help of Microsoft Artifact Registry (MAR) in PSResourceGet.
This enables customers to have a default trusted repository for modules and scripts printed by Microsoft.
That is constructed on high of the help we already added for Azure Container Registry (ACR)
Over time, we plan to usually help ORAS as an ordinary for storing artifacts in container registries, which might allow
help any container registry that helps the OCI distribution spec.
Home windows OpenSSH
We proceed to merge upstream OpenSSH adjustments into our Home windows OpenSSH distribution with previews printed to GitHub
and the ultimate launch up to date into Home windows.
DSC v3 useful resource
We proceed to develop a DSC v3 useful resource for SSHD_CONFIG with expectations that previews will probably be out there later this yr.
Desired State Configuration v3 (DSC)
We already introduced DSC 3.0 Common Availablity final month and have already got
two service updates out there.
DSC v3.0 is obtainable within the Microsoft Retailer or from our GitHub repo.
The macOS and Linux releases are curently solely out there from our GitHub repo.
DSC v3.1
As well as, we’re making speedy progress on a DSC v3.1 launch with a number of previews already out there.
Preview releases are additionally out there from the Microsoft Retailer or our GitHub repo.
You’ll be able to see what options are authorized or
being thought-about for the three.1 launch.
AI Shell
Our AI Shell challenge continues to make progress in the direction of integration of AI into the shell to
enhance productiveness.
Some additional enhancements being deliberate:
- Higher macOS help
- Enhanced Azure PowerShell help
- Enlargement of recent Brokers
- Higher integration with PowerShell
- Help for Mannequin Context Protocol (MCP)
Different tooling updates
We are going to proceed to handle reported points and merge group pull requests for the next initiatives:
- PowerShell VSCode extension
- PowerShell Script Analyzer
- others as wanted
Conclusion
Safety is our high precedence. We proceed to enhance the safety of how we ship software program. These enhancements aren’t seen to the group, however they make sure that we’re delivering safe software program.
We are going to proceed to work on the group’s high points and pull requests throughout our many initiatives, when doable.
We’re very grateful to our energetic group members!
