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
I have searched for my issue and not found a work-in-progress/duplicate/resolved issue.
I have not been informed if the issue is resolved in a preview version of the winget client.
Category of the issue
Side-By-Side installation.
Brief description of your issue
GitHub Desktop offers two update channels (stable and beta) - however, winget considers these as one channel. Therefore, beta users are offered updates that would move them to the stable channel. (GitHub Desktop's manifest is also a few versions behind, but I assume this will be resolved at some point.)
(Apologies if this is the wrong issue template - this seemed to me to be the best fit.)
Stable versions are listed as upgrades, despite the fact that they would move the user out of the beta channel.
Expected behavior
A new version should only be shown if it's a newer beta version, ensuring that users stay in the beta channel. This would be consistent with apps like Discord.
Environment
Windows Package Manager (Preview) v1.4.2161-preview
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.25201.1000
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.19.2161.0
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered:
ghost
added
the
Needs-Triage
This work item needs to be triaged by a member of the core team.
label
Sep 23, 2022
Rexogamer
changed the title
[Package Issue]: Split GitHub.GitHubDesktop into stable/beta channels
[Package Issue]: Updates for GitHub.GitHubDesktop don't distinguish between the stable and beta channels
Sep 23, 2022
Please confirm these before moving forward
Category of the issue
Side-By-Side installation.
Brief description of your issue
GitHub Desktop offers two update channels (stable and beta) - however, winget considers these as one channel. Therefore, beta users are offered updates that would move them to the stable channel. (GitHub Desktop's manifest is also a few versions behind, but I assume this will be resolved at some point.)
(Apologies if this is the wrong issue template - this seemed to me to be the best fit.)
Steps to reproduce
winget upgrade
Actual behavior
Stable versions are listed as upgrades, despite the fact that they would move the user out of the beta channel.
Expected behavior
A new version should only be shown if it's a newer beta version, ensuring that users stay in the beta channel. This would be consistent with apps like Discord.
Environment
Screenshots and Logs
No response
The text was updated successfully, but these errors were encountered: