Closed akshayjshah closed 4 years ago
CI failures seem to be the same flaky tests plaguing other PRs. @mjibson, mind taking a look and restarting tests if the change otherwise looks okay?
After thinking about this, I want to stay with the hard coded versions. There's some linter and check stuff that specifies the oldest version, and I think it's ok to have to bump occasionally.
Rather than pinning to specific Go minor releases, use the "stable" and "oldstable" aliases. These should always point to the most recent patch releases of the two officially-supported Go minor releases.
This should remove the need for PRs to update the Travis config every six months.