-
Notifications
You must be signed in to change notification settings - Fork 29
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
Difficulties downloading v0.2.0 #7
Comments
I got the following error from the CI pipeline of a branch where the dependency was automatically updated:
Not sure if or how this helps but it seems somewhat relevant |
Thanks Florian I suggest the v0.2.0 be retracted. |
Hmm - I'm not sure what happened, but this is the second time on one of my projects where the module differs. I just retracted v0.2.0 and cut v0.2.1. |
This issue has been automatically locked since there has not been any |
The release v0.2.0 clearly mentions:
v0.2.0
e436cb1
NewConstant
now returns a single valueI confirm that the code at tag
v0.2.0
/ commite436cb1
does include the new signature for NewConstant, as viewed in the GitHub web UI.However, when downloading v0.2.0 with
go get
(with a recent enough version of go), the downloaded codeHere is a full repro from Cloud Shell:
This is tricky.
I don't know the root cause of the problem. Might be a nasty bug in the go module tooling, or the way we use it. @sethvargo do you remember if you created the tag
v0.2.0
first at commit2ee2801
, then deleted it and created it anew at commite436cb1
?The text was updated successfully, but these errors were encountered: