-
-
Notifications
You must be signed in to change notification settings - Fork 62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to support Swashbuckle.AspNetCore v7.0.0 #150
Comments
and Swashbuckle.AspNetCore v7.0.0 is required to update to .net 9 |
I think this repo is abandoned. We probably need a new community fork of this with a new maintainer. |
@petriashev Hello. Do you think this is feasible? Is it okay if I create a PR? Thanks in advance for your effort. |
@petriashev Hello, I have opened a PR with the upgrade #151 Let me know if that works for you. |
I see 6.1 in |
@marcominerva the PR has been merged, you can now close the issue. |
Thank you! |
@marcominerva Hello, there is another problem - now with the depended package MicroElements.OpenApi.FluentValidation. |
@Jabulin I just realized the same thing, the process is not publishing MicroElements.OpenApi.FluentValidation to nuget. @marcominerva reopen the issue :( @avgalex any idea? Thanks in advance. |
What's happening is that it's only publishing that package (MicroElements.Swashbuckle.FluentValidation), but not the others (MicroElements.OpenApi.FluentValidation, MicroElements.NSwag.FluentValidation, etc). Maybe you could upgrade the version to 6.1.1 and try again? |
@jrgcubano is right, there is no MicroElements.OpenApi.FluentValidation 6.1.0 on nuget, but |
try to solve the problem with publishing the other packages |
@avgalex Now it works and I have successfully updated the MicroElements.Swashbuckle.FluentValidation package to version 6.1.0 in my project. |
Thank you @petriashev |
Currently, the library has the following constraint:
<PackageReference Include="Swashbuckle.AspNetCore.SwaggerGen" Version="[6.3.0, 7)" />
Now that Swashbuckle.AspNetCore v7.0.0 has been released, this prevents the update.
The text was updated successfully, but these errors were encountered: