+1

Just wondering as we might be facing this 'problem' aswell.

Is this issue related to Visual studio showing a NU1608 warning when including both the Microsoft.AspnetCore.OData (9.0.0) and Asp.Versioning.OData (8.1.0) ?

I presume the urgency of this request is because the package is intentionally clipped to not include 9.0+. For a bit of context and history, this is because I've been bitten too many times by OData since 5.x. Virtually every major version has broken things. By definition, this is allowed, but typically not expected. It's a double-edged sword and I haven't been able to handle the issues coming in that things broke. There have been numerous other occasions where OData minor versions or even patches have broken things. 😞

I've been really backed up with work and life of late, but I'm marching to carving out some time to get things going for everyone. I see the PR. I'll take a look as quickly as time allows.

Any news?
We are really waiting for it to upgrade everything.

Nice to see this finally closed 😄

Any ETA when we can expect this in the NuGet package?