4 ms·
> It's not like vgo makes it hard to upgrade all dependencies to their most recent version - it's done automatically with a single command, if you want it. And
by pcwalton 8y ago
> It's not like vgo makes it hard to upgrade all dependencies to their most recent version - it's done automatically with a single command, if you want it.
And how does it guarantee that this actually results in anything that works, if upper bounds are not supported?
- kaeshiwaza 8y agoUpper bound are major version, everything between should be api compatible (it's in the specs of go modules).
- pcwalton 8y agoExcept for version 0.x, and with vgo you have no recourse if somebody didn't follow the rules and made an incompatible change.
- jessaustin 8y agoThis is the whole point: just specify the version before the change, and it won't bother you.
- pcwalton 8y agoUntil someone actually wants to update their dependencies, writes "go get -u", and breaks the build.
- jessaustin 8y agoWell sure, you probably want to test after updating all of those dependencies. That's a good reason to only update when necessary. Do you argue that some other scheme prevents bugs in dependencies? That hasn't been my experience...