Why is the current Sourcetree version not available via Winget?

[Dirk Henkel]

The Sourcetree version 3.4.22 has been published a week ago now. Why is it still not available via the Windows packet manager Winget? As of now (2025-02-15), Winget still lists 3.4.21 as the newest available version.

When I asked a similar question for an earlier Sourcetree version (https://community.atlassian.com/t5/Sourcetree-questions/Why-isn-t-the-current-Sourcetree-version-available-via-Winget/qaq-p/2621261), I was told that the problem lies on the packet manager side.
But on the Winget side, I found the info that the workflow for updates is that the software developer uploads a manifest for the new version to the Winget repository: 
https://github.com/microsoft/winget-cli/discussions/2525

Since Sourcetree updates do eventually appear in Winget, I'm wondering whether submitting these manifests is not part of the regular Sourcetree release process - or does the approval on the Winget side indeed take that long?

[Dirk Henkel · Accepted solution]

Now I found it out myself, thanks to the Winget documentation in

• https://github.com/microsoft/winget-pkgs/blob/master/doc/README.md and
• https://learn.microsoft.com/en-us/windows/package-manager/package

And the answers are:

• The Winget manifest for the new Sourcetree version 3.4.22 has already been submitted.
• But the approval of a Winget manifest may indeed take a longer time (including discussion and corrections).
• And the process is publicly visible, like here for the Sourcetree version 3.4.22:
  https://github.com/microsoft/winget-pkgs/pull/227779