Feature Request: Prevent installations of incompatible PSEditions #71

Activity

1. edyoung commented on Apr 7, 2019

   

   Edwin Young (edyoung)

   on Apr 7, 2019

   More actions

   There are 2 mechanisms to specific PSEdition:

   1. The module manifest can explicitly include PSCompatibleEditions https://docs.microsoft.com/en-us/powershell/gallery/concepts/module-psedition-support). PowerShellGet will provide the behavior you want in this case (unless there's a bug I'm unaware of). However the downside is that PowerShell 4 and below will refuse to load the module at all with this value in the manifest. This is one reason why some modules don't include this.

   2. The module can include PSEdition_Desktop and PSEdition_Core tags. These are advisory only - PowerShell and PowerShellGet code doesn't pay any attention to them.

   So, module authors have the option to get the behavior you want. It's obviously possible to apply semantics to the tags as well but I'm a bit concerned that'd be a breaking change.

   Also possible: milder things like warn authors if they tag but don't set the edition in the manifest.
2. alerickson

   transferred this issue fromPowerShell/PowerShellGetv2on Mar 30, 2020
3. Sydney Smith (SydneyhSmith)

   added

   vNext

   Area-ErrorHandling

   on Mar 30, 2020
4. Steve Lee (SteveL-MSFT)

   added this to the vNext milestone on Sep 4, 2020
5. Steve Lee (SteveL-MSFT)

   removed

   vNext

   on Sep 4, 2020
6. ThomasNieto commented on Jul 11, 2023

   

   Thomas Nieto (ThomasNieto)

   on Jul 11, 2023

   Contributor

   More actions

   This should be an opt-in check like -AuthenticodeCheck. When -PSEditionCheck is passed then if CompatiblePSEditions is defined in the module manifest it uses that to validate editions. There could be some consideration if tags should be used if CompatiblePSEditions is not defined.