We’re excited to announce that an replace to our preview of PowerShellGet 3.0 is now accessible on the PowerShell Gallery!
This launch features a main refactor of the module to take away the dependency on the NuGet shopper APIs for distant repositories.
This model of the module, together with the PowerShellGet compatibility module, shall be delivery within the subsequent preview of PowerShell 7.4 (preview 3).
How you can Set up PowerShellGet 3.0 Preview 20
Conditions
Please guarantee that you’ve got the newest (non-prerelease) model of PowerShellGet and PackageManagement put in. To verify the model you at the moment have put in run the command Get-InstalledModule PowerShellGet, PackageManagement
The newest model of PowerShellGet is 2.2.5, and the newest model of PackageManagement is 1.4.7. To put in the newest variations of those modules run the next: Set up-Module PowerShellGet -Drive -AllowClobber
Putting in the Preview
To put in this preview launch side-by-side along with your present PowerShellGet model, open any PowerShell console and run: Set up-Module PowerShellGet -Drive -AllowPrerelease
What to anticipate on this replace
This replace strikes off of the NuGet shopper APIs and makes use of direct REST API requires distant repositories. It additionally consists of the beneath bug fixes.
Bug Fixes
- Updates to dependency set up
- Replace to retrieving all packages put in on machine
- PSResourceInfo model accurately shows 2 or 3 digit model numbers
- Utilizing
Discover-PSresource
with-CommandName
or-DSCResourceName
parameters returns an object with a correctly expanded ParentResource member Discover-PSResource
now not returns duplicate outcomesDiscover-PSResource
lists repository ‘PSGalleryScripts’ which doesn’t exist forGet-PSResourceRepository
Options to Anticipate in Coming Preview Releases
This module shouldn’t be but full. The main target for our subsequent preview launch is to maneuver off of the NuGet APIs for native repositories. For the complete record of points for our subsequent preview launch please discuss with our GitHub challenge.
How you can Observe the Improvement of this Module
GitHub is the perfect place to trace the bugs/function requests associated to this module. We’ve got used a mixture of tasks and labels on our GitHub repo to trace points for this upcoming launch. We’re utilizing the label Resolved-3.0
to label points that we plan to launch in some unspecified time in the future earlier than we launch the module as GA (usually accessible).
To trace points/options for the subsequent launch, please discuss with this GitHub challenge.
How you can Give suggestions and Get Assist
We can’t overstate how vital person suggestions is at this stage within the improvement of the module. Suggestions from preview releases assist inform design selections with out incurring a breaking change as soon as usually accessible and utilized in manufacturing.
So as to assist us to make key selections across the habits of the module please give us suggestions by opening points in our GitHub repository.
Sydney Smith
PowerShell Crew