-
-
Notifications
You must be signed in to change notification settings - Fork 362
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
Upgrade 'go-swagger/go-swagger' to avoid build error. #1179
Comments
Very odd. Let's see if there's any movement in this issue: go-swagger/go-swagger#3118 |
@alnr Thanks for your reply! I add some background information on the upstream issue, hope it can help. |
The oathkeeper build seems to work with the existing version, is there even a reason to upgrade? |
I guess you use So this issue more like a reminder in the hope that you can get rid of this problematic version of |
Ah, got it, thanks! Surely you must be curious why the version was re-tagged though? I don't have time to comb through the diffs in go-swagger since this event, so I'm hesitant to change versions now. |
Yeah, i guess maybe a minor mistake was found, they don't want to release a new version so they retagged it :).
No hurry, you can come back at this whenever possible. I'm using |
Preflight checklist
Ory Network Project
No response
Describe the bug
Currently
oathkeeper
depends ongo-swagger/go-swagger@v0.30.0
. Butgo-swagger
may have retagged version v0.30.0, so the checksum from the code in github does not match the checksum saved in sum.golang.org.So when trying to download
go-swagger
directly from Github, the following error will occur.Reproducing the bug
Run the following command.
Relevant log output
No response
Relevant configuration
No response
Version
0.40.7-pre.0
On which operating system are you observing this issue?
None
In which environment are you deploying?
None
Additional Context
github.com/go-swagger/go-swagger@v0.30.4
doesn't have such error, upgrade to v0.30.4 might be a good choiceThe text was updated successfully, but these errors were encountered: