You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While theoretically possible, vscode already has robust extension management and it can be handled via the command line --install-extension switch, so I would say this should go in the wontfix bucket as we'd have to own a manifest and keep it up to date.
Just to clarify the misunderstanding -- this issue is about upgrading PowerShell itself via WinGet, not the VS Code extension.
The extension already has an update notification feature (in UpdatePowerShell.ts) that detects new PowerShell releases and prompts users to open the GitHub release page. This feature request adds a WinGet upgrade option alongside "Open GitHub Release":
Activity
andyleejordan commentedon Apr 27, 2026
Are other VS Code extensions upgradeable with WinGet?
JustinGrote commentedon Apr 27, 2026
While theoretically possible, vscode already has robust extension management and it can be handled via the command line --install-extension switch, so I would say this should go in the
wontfixbucket as we'd have to own a manifest and keep it up to date.andyleejordan commentedon Apr 29, 2026
Agreed.
feat: add WinGet upgrade option to PowerShell update notification (Po…
PtJade-Ceramic commentedon Jul 21, 2026
Just to clarify the misunderstanding -- this issue is about upgrading PowerShell itself via WinGet, not the VS Code extension.
The extension already has an update notification feature (in UpdatePowerShell.ts) that detects new PowerShell releases and prompts users to open the GitHub release page. This feature request adds a WinGet upgrade option alongside "Open GitHub Release":
PR #5558 implements this.
feat: add WinGet upgrade option to PowerShell update notification (Po…