Skip to content

all: use Go 1.11.1 in CI#3298

Merged
ttaylorr merged 1 commit intomasterfrom
ttaylorr/go-1.11.1
Oct 8, 2018
Merged

all: use Go 1.11.1 in CI#3298
ttaylorr merged 1 commit intomasterfrom
ttaylorr/go-1.11.1

Conversation

@ttaylorr
Copy link
Contributor

@ttaylorr ttaylorr commented Oct 2, 2018

The latest release of Go, 1.11.1 was just published earlier today (on 2
October, 2018).

In the spirit of staying up-to-date with the latest version of Go (see
1), let's make sure that we continue to build correctly, even with the
very latest version.

1 moved the tip to Go 1.11, so there shouldn't be anything surprising
here.

/cc @git-lfs/core

The latest release of Go, 1.11.1 was just published earlier today (on 2
October, 2018).

In the spirit of staying up-to-date with the latest version of Go (see
[1]), let's make sure that we continue to build correctly, even with the
very latest version.

[1] moved the tip to Go 1.11, so there shouldn't be anything surprising
here.

[1]: 074a2d4 (all: use Go 1.11 in CI, 2018-08-28)
@ttaylorr ttaylorr requested a review from a team October 2, 2018 22:58
@ttaylorr ttaylorr added the review label Oct 2, 2018
@ttaylorr ttaylorr added this to the v2.6.0 milestone Oct 2, 2018
@ttaylorr ttaylorr merged commit dfc0f2f into master Oct 8, 2018
ttaylorr added a commit that referenced this pull request Oct 17, 2018
Since the advent of [1], and [2], we use Go 1.11 with modules enabled.
This relieves us of the requirement of having Git LFS checked out within
the appropriate location beneath the caller's $GOPATH.

So, let's remove the guideline, and recommend away from using `go get`,
since this command behaves differently based on whether or not its CWD
is itself a Go repository.

Instead, recommend that we use `git clone`, and do not specify a
location to perform the clone in, since Git LFS can be checked out from
anywhere.

[1]: dfc0f2f (Merge pull request #3298 from git-lfs/ttaylorr/go-1.11.1,
     2018-10-08)
[2]: 35fe301 (Merge pull request #3208 from git-lfs/ttaylorr/go-mod,
     2018-08-29)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants