We’re excited to announce that an replace to our preview of PowerShellGet 3.0 is now obtainable on the PowerShell Gallery!
Tips on how to Set up PowerShellGet 3.0 Preview 21
Conditions
Please guarantee that you’ve the most recent (non-prerelease) model of PowerShellGet and PackageManagement put in. To examine the model you at present have put in run the command Get-InstalledModule PowerShellGet, PackageManagement
The newest model of PowerShellGet is 2.2.5, and the most recent model of PackageManagement is 1.4.7. To put in the most recent variations of those modules run the next: Set up-Module PowerShellGet -Pressure -AllowClobber
Putting in the Preview
To put in this preview launch side-by-side together with your current PowerShellGet model, open any PowerShell console and run: Set up-Module PowerShellGet -Pressure -AllowPrerelease
What to anticipate on this replace
This replace strikes native repositories off of the NuGet APIs, this variation was made to allow future enhancements reminiscent of parallelization. This replace additionally consists of quite a lot of bug fixes.
On this replace we additionally made the choice to carry off on merging PowerShellGet previews into PowerShell 7.4 previews till June. This resolution was made as a result of we wish to be actually intentional about our resolution making course of with merging, or not merging, the compatibility module into PowerShellGet. At this time limit we’re exploring quite a lot of completely different choices relating to module compatilibity to take part on this converation please seek advice from this subject.
Options of this launch
New Options
- Transfer off of NuGet consumer APIs for native repositories
Bug Fixes
- Replace properties on PSResourceInfo object to Take away PackageMangementProvider property and make PowerShellGetFormatVersion property non-public
- Rename cmdlets
- Get-PSResource -> Get-InstalledPSResource
- New-PSScriptFileInfob -> New-PSScriptFile
- Check-PSScriptFileInfo -> Check-PSScriptFile
- Repair ValueFromPipelineByPropertyName on Save, Set up
- add Assist message for necessary params throughout cmdlets
- Repair model vary bug for Replace-PSResource
- Repair attribute bugfixes for Discover and Set up params
- Appropriate Surprising spelling of Surprising
- Resolve bug with Discover-PSResource -Sort Module not returning module
Options to Count on in Coming Preview Releases
This module is characteristic full however we’re persevering with to make bug fixes. For the complete record of points for our subsequent preview launch please seek advice from our GitHub venture.
Tips on how to Observe the Growth of this Module
GitHub is the most effective place to trace the bugs/characteristic requests associated to this module. We have now used a mix of initiatives 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 sooner or later earlier than we launch the module as GA (usually obtainable).
Timeline/Highway Map
Count on to see preview releases as bug fixes are made. Consumer suggestions will assist us decide once we can have a Launch Candidate model of the module which can be supported for use in manufacturing. Based mostly on person suggestions, if we imagine the three.0 launch is full, then we are going to publish a 3.0 model of the module as Typically Out there. Since these milestones are pushed by high quality, reasonably than date, we cannot provide an actual timeline at this level.
Tips on how to Give suggestions and Get Help
We can’t overstate how important 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 obtainable and utilized in manufacturing.
To be able to assist us to make key selections across the conduct of the module please give us suggestions by opening points in our GitHub repository.
Sydney Smith
PowerShell Workforce