-
Notifications
You must be signed in to change notification settings - Fork 127
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
go mod depends on 1.12 #79
Comments
Is the use of 1.12 negatively affecting you in some way? It's in RC1 so it's the default version of Go internally to Google at this point, so should be fine to use in pipelines. |
We use go 1.11 in all of our builds and don't wish to upgrade to 1.12 until
it's released. In general, it's probably wise for libraries to have a lower
bound on the go compiler version that they depend on since not all users
are able to upgrade.
…On Thu, Feb 21, 2019, 2:30 PM JP Robinson ***@***.***> wrote:
Is the use of 1.12 negatively affecting you in some way?
It's in RC1 so it's the default version of Go internally to Google at this
point, so should be fine to use in pipelines.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#79 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACu-MgY78GQEmup7E_kfFafjBDrU1pjqks5vPx3sgaJpZM4bIdOQ>
.
|
@jared2501 the version of go specified in go.mod is informative and doesn't actually do anything. It's used by Go to suggest that you may need to upgrade you version in case the module doesn't compile, but gziphandler doesn't actually require 1.12. See https://tip.golang.org/doc/go1.12#modules
|
Hmm I'm not seeing this on go 1.11:
|
If you're not keen to downgrade the suggested version, no worries, I can use the |
@jared2501 oh interesting. We can downgrade, but if the Go docs are telling the truth, the build is failing for some other reason and Go is trying to guess it's because of the language version? Is that code open source? |
(and if I have to guess, I'd go with golang/go#29278, which will likely require you to upgrade to Go 1.11.4) |
Reopening as we wait for more info. |
Ah nice one @fsouza, that was it! |
I upgraded to go 1.11.5, and could build v1.1.0 successfully |
Cool, thanks for confirming! It sucks that go swallows the original error message though, so let's keep |
The go module currently depends on an unreleased version of go. Can we bump the requires go version down to a released version?
The text was updated successfully, but these errors were encountered: