Right, any self import needs to change for the vgo case. (but not for
the go case unless you force everybody currently using your library to
start using semantic versioning paths)
-Nic
On Fri, Feb 23, 2018 at 10:06 AM, Zellyn Hunter wrote:
> On Fri, Feb 23, 2018 at 10:01 AM Nic Pottier wr
On Fri, Feb 23, 2018 at 7:59 AM, roger peppe wrote:
> As Russ pointed out to me, you can work around that by using a
> 0.0.0-2101234543-4f34f456eeefdcba version in your go.mod require
> section. If you've got that, it ignores the version tags.
Right, that works for clients of the library (and
Thanks for the great write up Dave, you've inspired me to "try harder" to
use it on a few of my projects after running into similar issues.
As you noted, my remaining big question mark is how existing libraries that
are above v1 transition to a vgo style while remaining backwards compatible
du
This is almost certainly because your .travis file is specifying your
version as `1.10` vs `"1.10"`
So your build is building with go 1.1 instead of 1.10.
Ran into this myself this morning.
-Nic
On Thursday, February 22, 2018 at 11:38:43 AM UTC-5, Владислав Митов wrote:
>
> Hey guys,
>
> One
