Specification: PowerShell Module Full Parity#6290
Draft
denelon wants to merge 3 commits into
Draft
Conversation
Specification for achieving full functional parity between the WinGet PowerShell module and the CLI, including SYSTEM context support, new cmdlets for configure/pin/download/repair/settings operations, and enhanced source management. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Trenly
reviewed
Jun 17, 2026
| // Pin management | ||
| interface IPackagePinManager | ||
| { | ||
| IAsyncOperation<IVectorView<PackagePin>> GetPinsAsync(); |
Contributor
There was a problem hiding this comment.
Implementation details at this level should be kept out of specificaitons, in my opinion. The inputs and outputs from the powershell cmdlets I understand, but the interface is a bit much
Trenly
reviewed
Jun 17, 2026
| ```powershell | ||
| # Intune remediation script | ||
| $pins = Get-WinGetPin | ||
| if ($pins | Where-Object { $_.Id -eq "Microsoft.Edge" -and $_.IsBlocking }) { |
Contributor
There was a problem hiding this comment.
Suggest $_.PinType instead of $_.IsBlocking for future expandability and for being able to check gating pins too
| - Azure Automation runbooks can manage packages across fleets | ||
| - Potential for a `WinGet` PowerShell drive provider (`Get-ChildItem WinGet:\installed\`) | ||
|
|
||
| ## Resources |
Contributor
There was a problem hiding this comment.
- Possibly also Bring Pinning to PowerShell Cmdlets #6190
WinGet ships two separate PowerShell modules: - Microsoft.WinGet.Client (package management) - Microsoft.WinGet.Configuration (configuration/DSC operations) Update spec to clearly delineate which cmdlets belong to which module, add Configuration-specific gaps (history, abort, delete), update the architecture diagram, and note module consolidation as a future consideration. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
- Remove detailed IDL interface definitions (too implementation-level for a spec; keep high-level description of needed COM surface) - Use PinType property instead of IsBlocking for future expandability (supports checking gating pins too) - Add PR microsoft#6190 (Configuration module improvements) to Resources Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
📖 Description
Specification for achieving full functional parity between the WinGet PowerShell module and the CLI. Covers new cmdlets for configure/pin/download/repair/settings, enhanced source management, and SYSTEM context support.
Authored with GitHub Copilot assistance.
🔗 References
Related Issues:
🔍 Validation
Spec document — no code changes to validate.
✅ Checklist
📋 Issue Type
Microsoft Reviewers: Open in CodeFlow