microsoft / microsoft/winget-pkgs

[Package Issue]: Updates for GitHub.GitHubDesktop don't distinguish between the stable and beta channels

Open
#80,610 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Bug
Dominant language
No language data
Stars
11.1k
Forks
9.7k
Avg merge
1h 32m
Merged PRs (30d)
376

Description

Please confirm these before moving forward
  • 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.)

Steps to reproduce
  • Install the beta version of GitHub Desktop here
  • Wait for a newer stable version to release
  • Run 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
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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the behavior with the GitHub Desktop beta from desktop.github.com/beta/ and winget upgrade, then inspect how the GitHub Desktop package manifest represents update channels. Done means a beta installation is offered only newer beta versions, not stable releases that would move it to the stable channel.

Written by the indexing model from the issue text.

Assessment

Domain
cli, release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.