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
v1.6.4 broke md2man - blackfriday? #598
Comments
Maybe you had better to upgrade go-md2man to v2.0.0 |
Same issue here. go-md2man is already at 2.0.0 |
Looks like the same issue here as well. Docker builds in our CI that were functional using |
Same issue for me. Go version 1.13
|
Until this is fixed, I started doing |
@rametta That was my approach as well, and it does prevent issues with "latest" breaking existing code functionality. The issue seems like the interdependencies of the latest v1.6.4 changed the target for go-md2man: v1.6.3
v1.6.4
|
How do I duplicate this error?
|
@ubogdan Looks like 1.6.4 regresses and remove the 1.6.3:
1.6.4
|
@josephzidell there is no way I can help sine you are giving me unuseful hints. Please run the above commands and paste me the results so I can make clue what it is about. |
@ubogdan Sure. It gets run in a docker-compose
|
@ubogdan I guess https://github.com/swaggo/cli/blob/v1.22.0/go.mod#L7 is the problem , however I wonder why it downloads "github.com/swaggo/cli v1.22.2" in the case "github.com/swaggo/cli v1.20.0" specified in go.mod |
@sdghchj I suspect the CI is cloning github.com/swaggo/ into $GOPATH/src/github.com/swaggo/ which is actually disabling VGO. |
thanks you guys promptly report this issue, I'm fixing it on #603. |
Describe the bug
Installation of latest version 1.6.4 fails and throws the following error.
To Reproduce
Install Latest version
95cdaaf
■ 1.6.4
Expected behavior
Install the previous version works well
Your swag version
1.6.4
Your go version
go1.12.5
The text was updated successfully, but these errors were encountered: