PowerShell / PowerShell/PSResourceGet
Update-PSModuleManifest should be Update-ModuleManifest
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 576
- Forks
- 114
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 7
Description
Prerequisites
- Write a descriptive title.
- Make sure you are able to repro it on the latest released version
- Search the existing issues.
Steps to reproduce
The Update-PSModuleManifest cmdlet should retain the PSGet v2 name of Update-ModuleManifest. Reasoning being is that the engine ships New-ModuleManifest and by changing the name you break the relationship with the two cmdlets. Secondly there should be any breaking changes that I'm aware of in v2 and v3 as the cmdlets perform the same work. Thirdly there is no issue with v2 and v3 having the same name cmdlet as both modules can be loaded at the same time.
@SydneyhSmith please let me know what you think on this. I'd like to fix this before GA.
Expected behavior
Update-ModuleManifest
Actual behavior
Update-PSModuleManifest
Error details
No response
Environment data
beta23
Visuals
No response
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 locating the Update-PSModuleManifest cmdlet and any related manifest-command tests or documentation. Confirm how the cmdlet is exposed and verify that the completed change uses Update-ModuleManifest without breaking the existing manifest workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100