[release/10.0] Update OpenApi to 2.7.5 - #67464

Please port to main as well

@wtgodbe main is on latest 3.x already (#66998)

Well, there was a newer version released for 3.x only 3 weeks ago. Let me update to 3.7.0: #67468

Looks like there's a test failure in OpenApiDocumentIntegrationTests.VerifyOpenApiDocument(documentName: "schemas-by-ref", version: OpenApi3_0)

@copilot Update the test so that it passes.

It looks like Microsoft.OpenApi might have changed some behavior - hopefully it's fine as long as it's correct and compliant with the spec.

@copilot Update the test so that it passes.

Updated the schemas-by-ref OpenAPI 3.0 snapshot in commit b158b60. The change reflects how OpenApi 2.7.5 serializes nullable schemas differently — nullable: true and the type are now emitted at the parent allOf level rather than as a separate sibling schema inside the allOf array. All 14 VerifyOpenApiDocument tests now pass.

/home/vsts/work/1/s/src/Components/test/E2ETest/ServerExecutionTests/ServerReconnectionWithoutStateTest.cs(14,28): error CS0234: The type or namespace name 'Communication' does not exist in the namespace 'OpenQA.Selenium.BiDi' (are you missing an assembly reference?) [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]
/home/vsts/work/1/s/src/Components/test/E2ETest/ServerRenderingTests/EnhancedNavigationTest.cs(12,28): error CS0234: The type or namespace name 'Communication' does not exist in the namespace 'OpenQA.Selenium.BiDi' (are you missing an assembly reference?) [/home/vsts/work/1/s/src/Components/test/E2ETest/Microsoft.AspNetCore.Components.E2ETests.csproj]

@copilot please fix

/home/vsts/work/1/s/src/Components/test/E2ETest/ServerExecutionTests/ServerReconnectionWithoutStateTest.cs(14,28): error CS0234: The type or namespace name 'Communication' does not exist in the name...

Fixed in the latest commit. The OpenQA.Selenium.BiDi.Communication namespace was removed in Selenium 4.44.0 (which this repo uses). The using directive in both files was unused — no types from that namespace were actually referenced in either file — so removing it is sufficient.

@wtgodbe The failures here appear to be flaky tests that were previously disabled in release/8.0 and release/9.0 (e.g #67243)

Can we quarantine the failures, or otherwise ba-g and merge as-is?

Can we quarantine the failures

Let's do that in a follow-up - mind opening a PR for that?

/ba-g failures are known flakiness

Hi @wtgodbe is this change likely to be in July or August release? Apologies not sure where I would need to look to find this info.

is this change likely to be in July or August release?

This will ship in the August release