What is the expected propagation time for a new package version?

[rob-nice]

Patch Tuesday has happened, Microsoft has dropped the .net SDKs 6.0.427 and 8.0.403.

I can see you've merged PRs for 6.0.427 and 8.0.403 but neither are yet available when running
winget upgrade --id Microsoft.DotNet.SDK.6
or
winget upgrade --id Microsoft.DotNet.SDK.8

This puts us ~10 and ~8 hours post merge, which seems slow - What is the expected propagation time? Is there any way for a consumer to see the state of a version release?

Source list as I suspect it may be relevant

> winget source list
Name    Argument                                      Explicit
--------------------------------------------------------------
msstore https://storeedgefd.dsx.mp.microsoft.com/v9.0 false
winget  https://cdn.winget.microsoft.com/cache        false

[mdanish-kh]

The usual propagation time is generally within an hour. You're seeing unexpected delay right now because the publish pipeline is failing at the moment. You can see the status labels from the repo's README.

Is there any way for a consumer to see the state of a version release?

This is generally tracked by the Publish-Pipeline-Succeeded label. The bot labels a merged PR with Publish-Pipeline-Succeeded when that PR has successfully gone through the pipeline. You can see right now that the PRs you linked above don't have that label. But sometimes when the pipeline is erroring out, the maintainers may kick off a manual publish run for the whole repo, and that may not attach this label.

[rob-nice]

That explains it, thanks for the detailed response!

[mdanish-kh]

FYI: The current issue is being tracked in:

• P.S.A Publishing Pipelines Failing #180404