-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Problem with swaggo/gin-swagger -> github.com/ugorji/go v1.1.5-pre #826
Comments
@nickarsar I fixed this in #825, but no release was made. For now you can use @ubogdan might make sense to release what's on master now Also, one word of caution on |
Can this thing be fixed in http-swagger as well, please :)? |
This is still an issue! To reproduce
|
yes, exactly. Shouldn't this be just matter of creating tag v1.1.5-pre or remove dependencies to it? |
@jakesyl oh, I missed that, thank you very much mate, it works 👏 |
#800 removes dependency on gin-swagger altogether so this should be fixed in the next release |
Removing github.com/ugorji/go as a dependency seems like a smart move. It's forever breaking downstream repos with tags being deleted and go module weirdness. This issue is currently blocking some of our builds - any ideas when it'll be released? The release is also a blocker for fixing this swaggo/http-swagger#36 Cheers. |
Update gin-swagger dependency version to mitigate issue with missing dep (github.com/ugorji/go v1.1.5-pre). Issue link: #826 Co-authored-by: Eason Lin <easonlin404@gmail.com>
Closing: fixed. |
Have problem with go mod download in project using swag:
go: github.com/swaggo/swag@v1.6.9 requires github.com/swaggo/gin-swagger@v1.2.0 requires github.com/ugorji/go@v1.1.5-pre requires github.com/ugorji/go/codec@v1.1.5-pre: reading github.com/ugorji/go/codec/codec/go.mod at revision codec/v1.1.5-pre: unknown revision codec/v1.1.5-pre
This helped me:
replace github.com/swaggo/gin-swagger v1.2.0 => github.com/swaggo/gin-swagger v1.3.0
Related issue: swaggo/gin-swagger#128
The text was updated successfully, but these errors were encountered: