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

Update to go 1.9.2 #9021

Merged
merged 6 commits into from
Oct 30, 2017
Merged

Update to go 1.9.2 #9021

merged 6 commits into from
Oct 30, 2017

Conversation

jwilder
Copy link
Contributor

@jwilder jwilder commented Oct 26, 2017

Required for all non-trivial PRs
  • Rebased/mergable
  • Tests pass
  • CHANGELOG.md updated
  • Sign CLA (if not already signed)

Updates to go1.9.2

@jwilder jwilder added this to the 1.4.0 milestone Oct 26, 2017
@ghost ghost assigned jwilder Oct 26, 2017
@ghost ghost added the review label Oct 26, 2017
@e-dard
Copy link
Contributor

e-dard commented Oct 26, 2017

@jwilder my only suggestion would be we switch out the 1.9 test runner for a 1.10 one. The 1.10 branch is open. I assume Circle doesn't fail the build if the testing-future-go-version runner fails does it?

@mark-rushakoff
Copy link
Contributor

There's a couple other mentions of Go versions that need to be updated. I'm locating those now and I'll drop them in here.

@jwilder
Copy link
Contributor Author

jwilder commented Oct 26, 2017

@e-dard It does fail the build.

@mark-rushakoff
Copy link
Contributor

@jwilder there's some go 1.8.4 occurrences in CONTRIBUTING.md that need updated, then I think this PR is good to go.

@jwilder
Copy link
Contributor Author

jwilder commented Oct 26, 2017

@mark-rushakoff Fixed

@@ -21,7 +21,7 @@ RUN gem install fpm

# Install go
ENV GOPATH /root/go
ENV GO_VERSION 1.9.1
ENV GO_VERSION 1.9.2
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The _go19 file isn't really necessary - it should be _go110 but I'm not sure whether that's available yet. I'm fine leaving the file around so we don't have to undo and redo the work to have circle test the next Go version.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah. I left it as is since I couldn't find a go1.10.

@e-dard
Copy link
Contributor

e-dard commented Oct 27, 2017

@jwilder dang. I guess we should probably hold the 1.10 runner off until the branch is a bit more stable.

@jwilder jwilder force-pushed the jw-go192 branch 2 times, most recently from 352d0c1 to d1edd76 Compare October 30, 2017 17:19
@jwilder jwilder merged commit 2217d04 into master Oct 30, 2017
@jwilder jwilder deleted the jw-go192 branch October 30, 2017 19:00
@ghost ghost removed the review label Oct 30, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants