PowerShell / PowerShell/PSResourceGet
Feature Request: Prevent installations of incompatible PSEditions
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
By default, modules that are marked as incompatible with the PSEdition in use should not be installed. The current behavior results unnecessarily in incompatible modules being installed and causing issues later.
Below, Posh-Git is given as an example, since it is tagged with PSEdition_Core, but can be installed, without any warning on WIndows PowerShell.
Ideally, both modules tagged with PSEdition_Core and not tagged with PSEdition_Desktop should result in an error (or at least a ShouldContinue prompt) when installed on Windows PowerSHell, and modules with PSEdition_Desktop but not PSEdition_Core should be similarly guarded from installation on PowerShell Core.
Steps to reproduce
In WIndows PowerShell:
Install-Module posh-git -AllowPrerelease
Expected behavior
Error saying that this module is incompatible with the current PowerShell Version
Actual behavior
Module is installed
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with Install-Module posh-git -AllowPrerelease in Windows PowerShell, then compare installation behavior with PowerShell Core. Done means incompatible modules are blocked with an error or a ShouldContinue prompt, including the inverse PSEdition case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100