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

build: Update travis to go1.7.5 and go1.8rc3 and Vagrantfile to go1.7.5 #11490

Merged
merged 2 commits into from
Jan 29, 2017
Merged

build: Update travis to go1.7.5 and go1.8rc3 and Vagrantfile to go1.7.5 #11490

merged 2 commits into from
Jan 29, 2017

Conversation

cblecker
Copy link
Contributor

No description provided.

@cblecker cblecker changed the title build: Update travis to go1.7.5 and go1.8rc3 build: Update travis to go1.7.5 and go1.8rc3 and Vagrantfile to go1.7.5 Jan 29, 2017
@stack72 stack72 added the build Auto-pinning label Jan 29, 2017
@jen20
Copy link
Contributor

jen20 commented Jan 29, 2017

Prior to this being merged, we need to ensure we won't get a repeat of the issues that plagued Go 1.8.4 with respect to root certificates on OS X when cross compiling - other than that, 👍

@cblecker
Copy link
Contributor Author

@stack72
Copy link
Contributor

stack72 commented Jan 29, 2017

@cblecker in that case, LGTM! Thanks :)

@stack72 stack72 merged commit c01680b into hashicorp:master Jan 29, 2017
@cblecker cblecker deleted the travis-goupdate branch January 29, 2017 19:43
@ghost
Copy link

ghost commented Apr 17, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
build Auto-pinning
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants