We’re excited to announce that an replace to our preview of PowerShellGet 3.0 is now out there on the PowerShell Gallery!
This launch consists of various bug fixes in addition to Get-PSScriptFileInfo
cmdlet.
The right way to Set up PowerShellGet 3.0 Preview 18
Conditions
Please observe that this preview launch of PowerShellGet 3.0 doesn’t assist PowerShell 7.0, 7.1 or 7.2-preview1.
It is a short-term subject as a result of a dependency and ought to be resolved in future releases. This launch does assist Home windows PowerShell 5.1, PowerShell 7.2 and seven.3.
Please guarantee that you’ve the newest (non-prerelease) model of PowerShellGet and PackageManagement put in. To examine 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 -Power -AllowClobber
Putting in the Preview
To put in this preview launch side-by-side together with your present PowerShellGet model, open any PowerShell console and run: Set up-Module PowerShellGet -Power -AllowPrerelease
What to anticipate on this replace
This replace fixes various bugs and provides assist for the Get-PSScriptFileInfo
cmdlet.
Options of this launch
- Add
Get-PSScriptFileInfo
cmdlet - Permit CredentialInfo parameter to just accept a hashtable
Bug Fixes
- Publish-PSResource now preserves folder and file construction
- Repair verbose message for untrusted repos gaining belief
- Repair for Replace-PSResource making an attempt to reinstall newest preview model
- Add SupportsWildcards() attribute to parameters accepting wildcards
- Carry out Repository belief examine when putting in a package deal
- Repair casing of
PSResource
inSet up-PSResource
- Replace .nuspec ‘license’ property to ‘licenseUrl’
Options to Count on in Coming Preview Releases
This module is just not but full. The main focus for our subsequent preview launch is bettering the efficiency of discover/set up by refactoring these cmdlets. For the total checklist of points for our subsequent preview launch please consult with our GitHub mission.
The right way to Monitor the Improvement of this Module
GitHub is one of the best place to trace the bugs/function requests associated to this module. Now we have 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 (typically out there).
To trace points/options for the subsequent launch, please consult with this GitHub mission.
Timeline/Street Map
Count on to see preview releases as new performance is added and bug fixes are made. Person 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 consumer suggestions, if we consider the three.0 launch is full, then we’ll publish a 3.0 model of the module as Typically Accessible. Since these milestones are pushed by high quality, reasonably than date, we cannot supply an actual timeline at this level.
The right way to Give suggestions and Get Help
We can not overstate how crucial consumer suggestions is at this stage within the growth of the module. Suggestions from preview releases assist inform design selections with out incurring a breaking change as soon as typically out there 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 Group