Hello team,
It's both frustrating and ironic to see how updating to Microsoft.OpenApi 2.0 ends up breaking an entire solution without any notice, warning, change log, or similar documentation. It's as if the update process has become: try it, if it breaks — revert; if it doesn't — you're lucky. These practices are steadily eroding the .NET ecosystem. Please, when similar changes are introduced, at the very least there should be explanations and actionable solutions offered to address such disruptive issues.
Hello team,
It's both frustrating and ironic to see how updating to Microsoft.OpenApi 2.0 ends up breaking an entire solution without any notice, warning, change log, or similar documentation. It's as if the update process has become: try it, if it breaks — revert; if it doesn't — you're lucky. These practices are steadily eroding the .NET ecosystem. Please, when similar changes are introduced, at the very least there should be explanations and actionable solutions offered to address such disruptive issues.