PowerShellGet 3.0 Preview 17 – PowerShell Group

Please be aware that this preview launch of PowerShellGet 3.0 doesn’t assist PowerShell 7.0, 7.1 or 7.2-preview1.

It is a non permanent concern 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-previews.

Please guarantee that you’ve the newest (non-prerelease) model of PowerShellGet and PackageManagement put in. To verify 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 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

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 -Drive -AllowPrerelease

When you have PowershellGet v3 already you possibly can run Replace-PSResource PowerShellGet -Prerelease

• Add -TemporaryPath parameter to Set up-PSResource, Save-PSResource, and Replace-PSResource
• Add String and SecureString as credential sorts in PSCredentialInfo
• Broaden acceptable paths for Publish-PSResource (Module root listing, module manifest file, script file)
• Add -Drive parameter to Register-PSResourceRepository cmdlet, to override an current repository
• Add a warning for when the script set up path isn’t in Path variable

• Change casing of -IncludeXML to -IncludeXml
• Replace precedence vary for PSResourceRepository to 0-100
• Editorial cross on cmdlet reference
• Repair concern when PSScriptInfo has no empty strains
• Make ConfirmImpact low for Register-PSResourceRepository and Save-PSResource
• Repair -PassThru for Set-PSResourceRepository cmdlet to return all properties
• Rename -FilePath parameter to -Path for PSScriptFileInfo cmdlets
• Repair RequiredModules description and add Discover instance to docs
• Take away unneeded inheritance in InstallHelper.cs
• Make -Path a required parameter for Save-PSResource cmdlet
• Enhance script validation for publishing and putting in

GitHub is the very best place to trace the bugs/function requests associated to this module. Now we have used a mix 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 sooner or later earlier than we launch the module as GA (usually accessible).

Count on to see preview releases as new performance is added and bug fixes are made. Consumer suggestions will assist us decide after 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 Obtainable. Since these milestones are pushed by high quality, reasonably than date, we cannot provide a precise timeline at this level.

We can’t overstate how crucial person 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 usually accessible and utilized in manufacturing.