Fixing bazelbuild/bazel/issues/7793

[BlueHotDog]

Making rules work for bazel > 0.26
not sure how to make this backwards comp.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[damienmg]

Hi, Bazel 0.27 is working at head according to our CI. Can you be a bit more specific on what is broken?

[BlueHotDog]

This is the relevant issue in Bazel:
bazelbuild/bazel#7793

[damienmg]

Ok that sounds good to me, thanks for sending this PR. We cannot accept your contribution if you do not sign the CLA.

[BlueHotDog]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[damienmg]

Ok I haven't realized but this is already in it. A few lines above in kwargs, the "ctx" argument is inserted on specific version of Bazel. I'll go ahead and close this PR.

Sorry for all the back and forth and I not realizing there was a Buildkite failure.