Closed damienmg closed 7 years ago
It looks like rules_dotnet are passing (e.g., http://ci.bazel.io/job/rules_dotnet/652/) and I can't figure out why they'd be depending on the rules_go release.
Sent https://github.com/bazelbuild/buildtools/pull/95 to update buildifier.
Oops sorry I should have written rules_web
On Mon, May 8, 2017 at 3:53 PM Kristina notifications@github.com wrote:
It looks like rules_dotnet are passing (e.g., http://ci.bazel.io/job/rules_dotnet/652/) and I can't figure out why they'd be depending on the rules_go release.
Sent bazelbuild/buildtools#95 https://github.com/bazelbuild/buildtools/pull/95 to update buildifier.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bazelbuild/bazel/issues/2956#issuecomment-299873031, or mute the thread https://github.com/notifications/unsubscribe-auth/ADjHf8HaxKoh8-wDoUTT77CYSTiJ7lXWks5r3x5ogaJpZM4NSG76 .
Ah, got it. Sent https://github.com/bazelbuild/rules_webtesting/pull/115.
Due to upstream rules_go not including PR https://github.com/bazelbuild/rules_go/pull/428 in the release. Filing this bug for hand off mostly, the fix is no longer on our side.
/cc @c-parsons fyi