Skip to content

Update Microsoft.OpenApi to 3.6.0 - #66998

Merged
Youssef1313 merged 2 commits into
mainfrom
dev/ygerges/openapi-update
Jun 3, 2026
Merged

Update Microsoft.OpenApi to 3.6.0#66998
Youssef1313 merged 2 commits into
mainfrom
dev/ygerges/openapi-update

Update YamlReader as well

55bd741
Select commit
Loading
Failed to load commit list.
Build Analysis / Helix Queue Insights (preview) succeeded Jun 4, 2026 in 0s

View the current status of Helix

Details

Pipeline Status

The list of queues is cached weekly. If your PR changes what queues your pipelines use, this information will not show the updated queues.

Estimated Pipeline Durations

This model assumes that the current state of the entire CI infrastructure is normal, and that your CI pipelines will succeed.

Pipeline Lower Bound Estimated Time Upper Bound
aspnetcore-template-tests-pr 1 hour, 24 minutes, 1 second 1 hour, 39 minutes, 1 second 1 hour, 54 minutes, 1 second
aspnetcore-ci 40 minutes, 49 seconds 1 hour, 11 minutes, 21 seconds 1 hour, 41 minutes, 53 seconds
aspnetcore-components-e2e 1 hour, 9 seconds 1 hour, 4 minutes, 57 seconds 1 hour, 9 minutes, 46 seconds

Highest Work Item Wait Time Queues

Here's a list of the top 3 queues with the highest work item wait time:

Queue Work Item Wait Time Difference in Moving Avg
osx.15.amd64.open 5 hours, 16 minutes, 59 seconds 0.44% 📈
windows.amd64.vs2026.pre.scout.open 32 minutes, 29 seconds -0.12% 📉
ubuntu.2404.amd64.open 14 minutes, 30 seconds -0.54% 📉

Grafana Dashboard

For more in-depth information on the status of Helix, visit our Grafana Dashboard.

Your Queues

☁️ Helix Queues

dotnet/aspnetcore is currently configured to submit to the following Helix queues:

🏢 On Premises Helix Queues

dotnet/aspnetcore uses the following on-prem queues:

Build Pools

Was this helpful? Yes No