Repository navigation
please tag 3.0 nuget package as pre-release since according to docs it is incompatible with latest .net 10 release #2598
Description
Activity
Hi Nova-Logic
Thank you for using the SDK and for reaching out.The way a nuget package is "tagged as a pre-release" is through its version number (addition of a "-suffix").
This gets superseded by any other version with the same major version number and no suffix.Essentially what that means is because we've already published a 3.0 version with no suffix, nuget/dotnet package manager/dependabot would always resolve to version 3.0 even if we published a pre-release now.
The only way around that would be to:- unlist the version 3
- publish a version 4 preview
Which at this point would probably create more confusion.
I also want to address the point of "not supported on .net9 or 10". What's not supported is with the aspnetcore openapi integration v9 or 10. Anything else works, like a console app for instance.
Swashbuckle swagger is also working on an additional release to support v3.
The main thing we could do at this point is probably to ensure the documentation/release notes are clear enough so any developer with similar questions can easily find answers and choose the version that's right for their context. Don't hesitate to outline any gap on this front.
Let me know if you have any additional comments or questions.
I've authored #2602 in an effort to provide additional details on the topic.
Is your feature request related to a problem? Please describe.
Currently it 3.0 nuget package is suggested as upgrade even while it is not supported on .net 9 or .net 10
Describe the solution you'd like
A clear and concise description of what you want to happen.
please tag 3.0 nuget package as pre-release package since according to docs it is incompatible even with latest .net 10 release.
Describe alternatives you've considered
As a workaround every developer can exclude openapi from upgrade, but I assume that is not how it should be done