Why does the Store app lag behind so much?

[github-account1111]

The Store version of the App Installer (so probably the most common version of winget) hasn't been updated since October and is still stuck on version .350:

That is despite multiple newer stable versions having been released on GitHub, latest one being .460.

Funnily enough, according to winget itself, the latest stable version is .440 which is somewhere between what the Store and the repo shows:

> winget upgrade
Name                        Id                          Version                     Available                    Source
-----------------------------------------------------------------------------------------------------------------------
...
App Installer               Microsoft.AppInstaller      1.27.350.0                  1.27.440.0                   winget
5 upgrades available.

The following packages have an upgrade available, but re...

IDEK if I should update winget with winget, but why all the discrepancies between the different distribution channels?

[florelis]

The last three stable builds are .350, .440 and .460.

.440 was the previous stable version, released about two or three weeks ago, so the Store having .350 was on the latest until recently.

.440 was released to GitHub and the winget source, but I forgot to publish it to the Store. (It was actually uploaded and submitted for certification, but I missed the final step after that.) It takes several days for us to start seeing an uptick in the share of installed versions after a release, so by the time we noticed it wasn't rolling out, we were already close to publishing .460.

.460 was released to GitHub and the Store today, less than an hour before your post. It probably hadn't updated at that point there.
We will wait a few days before updating it in the winget source (winget-pkgs) due to a bug when winget updates itself, to allow as many updates as possible to go through the Store instead. (This bug is fixed in .460.)