[ntyrrell]

Upgraded Microsoft.Extensions.ApiDescription.Server & Microsoft.Extensions.ApiDescription.Client to 9.0.3

This would update the runtime dependencies (which are still dependent on AspNetCore 6.0.3) as well as the following bugfixes for Microsoft.Extensions.ApiDescription.Server:
Fix up packaging for Extensions.ApiDescription.Server
Fixes for OpenAPI document generation with M.E.ApiDescription.Server
Upgrade to Microsoft.OpenApi 2.x and support OpenAPI v3.1
#59749 move TrimEnd after path normalization
And the following for Microsoft.Extensions.ApiDescription.Client:
#59749 move TrimEnd after path normalization
Fix duplicate add of items to Compile on Microsoft.Extensions.ApiDescription.Client.targets

[lahma]

I think you can get these also by just referencing the latest versions in the consuming project?

[ntyrrell]

I think you can get these also by just referencing the latest versions in the consuming project?

Sure, but I don't think that it's unreasonable for this project to reference the most up-to-date version.

It also puts more onus on the consumer of this library to have to maintain an additional dependency.

[RicoSuter]

Not sure whether this is a good idea, i think this might break e.g. .NET 8 users...
Isnt this package's version defined by the host application?

[lahma]

My intuition would say that lowest non-vulnerable LTS would be a good approach, like 8.0.0. Some corporates might get confused if they are tied to say NET 8 LTS and 9.x dependencies start to show up.

[RicoSuter]

Thats probably a feasible approach.. (.net 8)
I think this apidescription stuff will be anyway deprecated longterm..

[ntyrrell]

Thanks for the feedback. I'll adjust it to 8.0.* (not sure what the latest patch number is off hand)

[RicoSuter]

Thanks for the PR.