When is an update available on winget? #25441
-
|
According the official documentation its recommended to use winget I am a newbie to powershell, know some basics but nothing really about winget and stuff. Then I try |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 4 replies
-
|
Similarly, is there any particular reason StableReleaseTag and ReleaseTag have not been updated? |
Beta Was this translation helpful? Give feedback.
-
|
Edit to answer original question. If you are comfortable with winget that's fine to use. On Windows, both the Windows Store and the downloadable installers have self-updating options. For the Windows Store updates in my experience came out a the earliest of the auto-updating options. The MSI version has options to stay current with Windows Update, and gives great feedback when running interactively. I rarely wait long enough to observe Windows Update actually updating my installs, but have observed that it does work.
or to output just the hash:
B110ECCAF55BB53AE5E6B6DE478587ED8203570B0BDA9BD374A0998E24D4033A |
Beta Was this translation helpful? Give feedback.
-
|
@skoenfaelt - Having this get asked on just about every version in the last year or so, with these being some of the ones I've commented on The same applied to any other package manager & Updates Via Microsoft Update. This discussion is a Duplicate of the issue #25457 & as such I am closing this as a duplicate especially as WinGet does now show PowerShell 7.5.1 |
Beta Was this translation helpful? Give feedback.
-
|
as an aside - since this gets asked so often... It might be useful to have an official document describing the release process and the artifacts generated where and when. This should cover direct release via Github, Vis the Store, Choocolately, and via WinGet. And as a reply to the OP, I personally use the Install-PowerShell.ps1 script/. This gets a new release of PowerShell. This is, for me, considerably easier than using/waiting for the Store or Winget. |
Beta Was this translation helpful? Give feedback.
-
|
Note we're in the same situation w/ 7.6.0-Preview.6: Open terminal->PwshSession. See note that new preview is out. Run winget update. Mentally note "I wonder how long before winget gets the new one". Visit this here repo and look for issues/discussions. I see that the last commit for the pwshbot/winget-pkgs repo is for preview 6, and there's an open PR with a failed validation run. (With the somewhat typical AzDOS pipeline issue of error output being "less than optimal." :) So it looks like we're further along on getting new releases automagically packaged and published, but still with some speedbumps. I will emphasize that those that are testing previews are the most likely to be using something like Winget, so making the publish/upgrade process as frictionless as possible would help everyone. |
Beta Was this translation helpful? Give feedback.
@skoenfaelt - Having this get asked on just about every version in the last year or so, with these being some of the ones I've commented on
It is usually around a week between PowerShell Team Releasing to GitHub -> the PR that releases to WinGet is accepted into this repo from the team
This is a mix what I think (looking from the outside) to be a manual process by PSTeam to raise a PR to the WinGet repo and the WinGet Team accepting that PR & as such is always delayed slightly.
The same applied to any other package manager & Updates Via Microsoft Update.
This discussion is a Duplicate of the issue #25457 & as such I am closing this as a duplicate especially as WinGet does now show PowerSh…