PowerShell / PowerShell/PSResourceGet
Feature request: allow some module to stick to pre-release version
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
I've installed some modules with pre-release version, some not. Here is the problem, if I want to update all module, I have to:
Update-module
Update-module -Name $prerelease module -Allowprerelease
I think this can definitely be done by introduce set-module or update-module config by setting some module stick to prerelease, others not(this can include some pre-release module)
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 reading the existing Update-Module behavior, especially how -AllowPrerelease is applied, and compare it with the requested Set-Module or Update-Module configuration. Define how a module-specific prerelease preference should be stored and how updating all modules should honor mixed preferences; done means prerelease-pinned modules update without the extra command while other modules retain current behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, powershell
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100