The release-1.12 branch requires bazel 0.17.1+ now #72262
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
/kind bug
What this PR does / why we need it: in #71675 I inadvertently required a slightly newer bazel, as one of the attributes I was using was first added in bazel 0.17.1.
I've already updated the version of bazel we use for this branch on Prow in kubernetes/test-infra#10350, but I keep getting bit by not using the right bazel version in other places. By updating this check, it becomes a little easier to debug.
Does this PR introduce a user-facing change?:
/assign @BenTheElder @feiskyer