PowerShellGet shipping in PowerShell 7.4

Summary of the new feature / enhancement

• PowerShellGet v3 (-PSResource cmdlets) will be renamed to PSResourceGet begining with the next release (beta22).
• PowerShell v7.4 (LTS) will ship PSGet v2.2.5 and PSResourceGet v3.0.x. This will help us get telemetry about usage of PSResourceGet. No compat layer will be shipped. This allows current scripts to work as is, with or without fully qualified cmdlet names.
• Customers can use -PSResource cmdlets for perf improvements and new features. No new feature work will be done in -Module cmdlets.
• In the first preview of PowerShell v7.5 we include CompatPowerShellGet renamed as PowerShellGet v3.0.0 in addition to PSResourceGet. In PowerShell v7.5 we will not ship PowerShellGet v2.2.5 side by side.
• We will get feedback from community about the compat layer which will help use decide on our future course.
• When time comes, we ship PSResourceGet in addition to current PowerShellGet 1.0.0.1 in Windows PowerShell.
• We will also work with Windows to improve the current Install/Upgrade experience in Windows PowerShell.

Proposed technical implementation details (optional)

No response

[ajansveld]

I think the Microsoft.PowerShell.PSResourceGet rename (and shipping it side-by-side) is a great idea, but at that point can we also just drop the “Get” part? Seems to make sense since:

• The name is inconsistent with general module naming practices
• The module does more than “get”
• (Most of) the cmdlets have the PSResource prefix

Vote for Microsoft.PowerShell.PSResource!

[ThomasNieto]

Since you’re going to renaming the module will you be putting it in the Microsoft.PowerShell module prefix?