Go vgo: Semantic Versioning and Human Error

Re:Go vgo: Semantic Versioning and Human Error by RVuRnvbM2e on Monday May 21, 2018 @11:25PM (#17123497)

> So what's happened here is there's a bug in in gRPC 1.8.

Yeah I don't understand how this is vgo's problem.

In the follup post it shows that they are importing the buggy gRPC version directly: https://codeengineered.com/blog/2018/golang-vgo-broken-dep-t...

So doesn't that mean that they can just file a bug report upstream to get the regression fixed in 1.8.1, and exclude 1.8.0 in the meantime?

[ Parent | on HN ]

Re:Go vgo: Semantic Versioning and Human Error by dolmen on Tuesday May 22, 2018 @12:52AM (#17123799)

I agree. I don't see a vgo issue.

The behavior in the example was broken by a release, but could have as well been restored by a patch release as restoring behaviour would not have broken the API.

See https://news.ycombinator.com/item?id=17123583

[ Parent | on HN ]