PiperOrigin-RevId: 306572687
Change-Id: I49448295cdd088eb114a7d518dd0db1822f2d7a6

This is necessary to start using bazel's experimental cc_shared_library support.
This change is part of the refactoring described in https://github.com/tensorflow/community/pull/179

PiperOrigin-RevId: 294736824
Change-Id: I8d13c71545cf2f2edd47818b40fa413e3e9c3254

This is necessary to start using bazel's experimental cc_shared_library support.
This change is part of the refactoring described in https://github.com/tensorflow/community/pull/179

PiperOrigin-RevId: 288808507
Change-Id: Ie78fb4ff8dad128ebef280037cce4d3c4f42addc

PiperOrigin-RevId: 279959797
Change-Id: Ic5785033bc735d388f368aebee891160781fb193

Follow up of cl/274686963

RELNOTES: If you're building Tensorflow from source, consider using bazelisk (https://github.com/bazelbuild/bazelisk) to automatically download and launch the correct Bazel version. Bazelisk reads the `.bazelversion` file at the root of the project directory.
PiperOrigin-RevId: 274840419
Change-Id: Idae8abf7014b0a593c36068603512545c0f3dfaf

Add a .bazelversion file to support automatically using the recommended Bazel version via Bazelisk, the official Bazel wrapper.

https://github.com/bazelbuild/bazelisk

With this file, bazelisk users never need to care about manually installing the
right version of Bazel. bazelisk takes care of the version switching
autamtically.

Alternatively, bazelisk users can also set the USE_BAZEL_VERSION environment
variable.

PiperOrigin-RevId: 274686963