We are maintaining a repository that uses Microsoft.AspNetCore.OpenApi together with Microsoft.OpenApi. We would like to validate builds on the local SDK and next LTS SDK, and we are currently blocking Microsoft.OpenApi updates above 2.3.9 until compatibility is confirmed.
Could you please add or document upstream compatibility coverage for Microsoft.OpenApi versions above 2.3.9 in the ASP.NET Core OpenAPI source generation scenario? A small integration test around source generation would make this much easier to validate and would help avoid regressions for consumers.
Relevant context:
- Package: Microsoft.OpenApi
- Scenario: OpenAPI source generation / ASP.NET Core integration
- Current constraint: keep updates at or below 2.3.9 until compatibility is validated
We are maintaining a repository that uses Microsoft.AspNetCore.OpenApi together with Microsoft.OpenApi. We would like to validate builds on the local SDK and next LTS SDK, and we are currently blocking Microsoft.OpenApi updates above 2.3.9 until compatibility is confirmed.
Could you please add or document upstream compatibility coverage for Microsoft.OpenApi versions above 2.3.9 in the ASP.NET Core OpenAPI source generation scenario? A small integration test around source generation would make this much easier to validate and would help avoid regressions for consumers.
Relevant context: