Update SharpYaml dependency to v3.x

[denisbredikhin]

Is your feature request related to a problem? Please describe.

OpenAPI.NET currently depends on SharpYaml v2. In my project, I use OpenAPI.NET to process OpenAPI documents and also need to read additional YAML-based configuration files.

SharpYaml v3 is a major redesign that introduces breaking changes compared to v2. Since OpenAPI.NET brings SharpYaml v2 as a dependency, I am currently forced to continue developing against the older SharpYaml API and plan a future migration.

Describe the solution you'd like

I would like OpenAPI.NET to update its SharpYaml dependency from v2 to the latest v3 release.

Describe alternatives you've considered

• Continuing to use SharpYaml v2 in my own code and migrating later.
• Isolating YAML processing behind an abstraction layer to minimize the impact of a future migration.
• Using a different YAML library for application-specific configuration files.

While these approaches are possible, they add complexity that could be avoided if OpenAPI.NET adopted SharpYaml v3 directly.

[baywet]

Hi Denis,
Thank you for using the SDK and for reaching out.

Unfortunately, this would be a major breaking change for consumers as well, which mandates doing that in the next major version of Microsoft.OpenAPI.
We currently have no plans for a new major version, although a few other cleanup items (see TODOs in the code) would go along with that kind of change.
The release of OpenAPI 3.3 and implementation in this library might require a new major version, at that time we'll evaluate other breaking changes to include.

Let me know if you have any additional comments or questions.

[denisbredikhin]

Hi Vincent. Sure, I understand all these obstacles and don't expect quick solution.
Please consider this request when you will be working on a new major version.