Automated g4 rollback of changelist 392771263

PiperOrigin-RevId: 392795427

Author: pichuan

.bazelrc

@@ -9,6 +9,9 @@
 # installed in a specific location, and there doesn't seem to be a
 # way to refer to it symbolically, like BUILD files can.)
 import %workspace%/../tensorflow/.bazelrc
+# In tensorflow/.bazelrc v2.6.0, setting this to false broke our build.
+# So, setting it back to true.
+build:linux --distinct_host_configuration=true
 
 # Use 128 jobs to build. Unfortunately there doesn't seem to be any way to set
 # the number of jobs to the number of actual cores on the machine (e.g., by

README.md

@@ -80,7 +80,7 @@ Note that install.sh extensively depends on apt-get, so it is unlikely to run
 without extensive modifications on non-Debian-based systems.
 
 Nucleus depends on TensorFlow. By default, install.sh will install a CPU-only
-version of a stable TensorFlow release (currently 2.5). If that isn't what you
+version of a stable TensorFlow release (currently 2.6). If that isn't what you
 want, there are several other options that can be enabled with a simple edit to
 `install.sh`.
 
@@ -99,6 +99,7 @@ This is Nucleus 0.6.0. Nucleus follows
 
 New in 0.6.0:
 
+*   Upgrade to support TensorFlow 2.6.0 specifically.
 *   Upgrade to Python 3.8.
 
 New in 0.5.9:

install.sh

@@ -31,7 +31,7 @@
 # ------------------------------------------------------------------------------
 
 NUCLEUS_BAZEL_VERSION="3.7.2"
-NUCLEUS_TENSORFLOW_VERSION="2.5.0"
+NUCLEUS_TENSORFLOW_VERSION="2.6.0"
 
 function note_build_stage {
   echo "========== [$(date)] Stage '${1}' starting"