Supports bazel 0.3.0? about rules_go HOT 3 CLOSED

I typically build @ HEAD, so I was not aware of that. I made the change to
"host" to eliminate the 'deprecated' message we were getting.

On Wed, Sep 21, 2016 at 3:36 PM, Paul Cody Johnston <
[email protected]> wrote:

I'm curious if rules_go is being tested against 0.3.0 in a CI matrix. On
travis https://travis-ci.org/pubref/rules_protobuf/jobs/161725410, I'm
now getting:

/home/travis/.cache/bazel/external/io_bazel_rules_go/go/def.bzl:500:18: expected ConfigurationTransition or NoneType for 'cfg' while calling label but got string instead: host.

Which seems related to changing the cfg attributes from HOST_CFG to "host".
So, I'm thinking of dropping 0.3.0 from my build matrix and requiring 0.3.1
instead.

Perhaps I've missed something so I thought I'd bring it up here.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#113, or mute the thread
https://github.com/notifications/unsubscribe-auth/ALF-0puic0tSvg2FWhzZJQ-JzNIRJ599ks5qsYclgaJpZM4KDMZs
.

from rules_go.

Looks like @jart brought this up a few days ago in bazelbuild/bazel#1788.

from rules_go.

I didn't intentionally dropped support of 0.3.0. But it would be reasonable to say that rules_go doesn't support 0.3.0 because 0.3.1 was released two months ago.

from rules_go.