Winget Version Outdated: Topgrade 14.0.1 Instead of 16.0.1

[niStee]

Erroneous Behavior

The version of Topgrade in Winget is 14.0.1 instead of the current release level 16.0.1.

Expected Behavior

The version of Topgrade in Winget should match the latest release version, which is 16.0.1.

Steps to reproduce

1. Check the version of Topgrade available in Winget by running winget show topgrade, or https://winstall.app/apps/topgrade-rs.topgrade.
2. Compare it with the latest release version on the Topgrade GitHub releases page https://github.com/topgrade-rs/topgrade/releases/.

Possible Cause (Optional)

The .github/workflows/update_winget.yml workflow may not be correctly configured to update the Winget package with the latest version.

[SteveLauC]

Indeed, thanks for bringing this to our attention!

Here is the log of that action:

if (-not $?) {
    Write-Output "::error::Package $PkgId does not exist in the winget-pkgs repository. Please add atleast one version of the package before using this action."
    exit 1
  }

[niStee]

I will look into it.

[soredake]

Any progress on this?

[niStee]

Any progress on this?

#976

[niStee]

Indeed, thanks for bringing this to our attention!

Here is the log of that action:

if (-not $?) {
    Write-Output "::error::Package $PkgId does not exist in the winget-pkgs repository. Please add atleast one version of the package before using this action."
    exit 1
  }

@SteveLauC, the following may be the problem here vedantmgoyal9/winget-releaser#309 (comment), any suggestions on how to fix this?

[SteveLauC]

the following may be the problem here vedantmgoyal9/winget-releaser#309 (comment), any suggestions on how to fix this?

Honestly, I don't think I understand this issue. But per the README, looks like we don't need to use fork-user input?

Fork microsoft/winget-pkgs under the same account/organization as the project's repository. If you are forking winget-pkgs on a different account (e.g. bot/personal account), you can use the fork-user input to specify the username of the account where the fork is present.

I do find something strange, our winget-pkgs is fork not up-to-date with the upstream repo(I just manually gave it an update), it is possibly because this:

GitHub actually has reached out to me specifically about the winget-pkgs repo and its forks causing some issues within their backend systems which could be the cause of failed merges which has downstream effects on Pull.

Though I have no idea if this could lead to a failed release.