Update bazel toolchains to 3.2.0 to support current Bazel release #8386
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
AutomatedTester
approved these changes
Jun 4, 2020
titusfortner
pushed a commit
to titusfortner/selenium
that referenced
this pull request
Aug 13, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Bazel 3.2 has been released so a bump to the toolchains is needed to allow the toolchain to work with Bazel 3.2. The SHA256 has come from the toolchains GitHub page at https://github.com/bazelbuild/bazel-toolchains/releases/tag/3.2.0
Motivation and Context
Building with the latest Bazel release fails due to bazel-toolchains not recognizing the 3.2.0 version code from Bazel.
Types of changes
Checklist