Skip to content
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

Fix go.mod for Go 1.13+ #3

Merged
merged 1 commit into from
Jan 10, 2020
Merged

Fix go.mod for Go 1.13+ #3

merged 1 commit into from
Jan 10, 2020

Conversation

nlowe
Copy link

@nlowe nlowe commented Sep 24, 2019

Go 1.13 introduces stricter version checks. The timestamp for v0.0.0 dependencies must match the timestamp of the commit. I've also disabled GO111MODULE in the Makefile when we install tools. Without this Go wants to pull in all of their dependencies, and there's tons of breaking package renames that I don't feel like fighting with (it also adds a ton of time to the build).

@nlowe nlowe added the bug Something isn't working label Sep 24, 2019
@nlowe nlowe requested a review from a team September 24, 2019 19:16
Go 1.13 introduces stricter version checks. The timestamp for v0.0.0
dependencies must match the timestamp of the commit.

Additionally, don't try to install tools with go modules support.
@nlowe
Copy link
Author

nlowe commented Oct 25, 2019

@HylandSoftware/devops Please take a look at this when you get some time.

@jhindulak jhindulak merged commit 934aae3 into master Jan 10, 2020
@nlowe nlowe deleted the feat/fix-go-mod branch January 10, 2020 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants