v1.7.0

This Bazelisk release contains the following changes:

• 🏗️ Refactoring for easier maintenance and better test coverage. (#151)
• 🦠 Workaround against being detected as a virus on Windows. (#162)
• 💯 Fixed a bug where Bazelisk would crash when two Bazel releases were in "release candidate" state at the same time and we used the GCS-based fallback to detect the version. (#170)

Thanks @fwe for the contributions!

v1.6.1 (small but important bug fixes)

This Bazelisk release fixes two reported bugs:

• 📁 Correctly handle the case when tools/bazel is a directory by ignoring it instead of crashing. (#148)
• 🌌 Correctly prepend the Bazel binary to the PATH on Windows. (#149)

Thanks @Kiougar and @coeuvre for the contributions!

v1.6.0 (arm64 support, .bazeliskrc, PATH fix)

This Bazelisk release brings two improvements:

• 🦾 Bazelisk now supports arm64 on Linux. Note that Bazel 3.4.0 was the first release with arm64 binaries. Thanks for the contribution @lizan!
• 🌌 Bazelisk now runs Bazel with a $PATH set so that running the bazel command resolves to the correct Bazel version. For example, this is useful if you have shell scripts or tests that invoke bazel - these will now pick the right version of Bazel. Thanks for the contribution @coeuvre! (#111)
• 📝 Bazelisk now supports reading config values from a .bazeliskrc file. Thanks @zellyn! Docs for this feature are here: https://github.com/bazelbuild/bazelisk#bazeliskrc-configuration-file (#127)

Known issues:

• 💔 This release is broken on Windows due to #149. A fix will be released in v1.6.1.

v1.5.0 (GCS fallback)

This Bazelisk release contains a feature that improve reliability:

• 🆘 When Bazelisk cannot fetch Bazel's version history from GitHub's API, it will instead try to get it from metadata stored in Bazel's Google Cloud Storage bucket.

v1.4.0 (npm improvements, Starlark incompatible flags)

This fresh Bazelisk release brings two improvements:

• ✨ Add bazel as a binary in the NPM package JSON. When you install Bazelisk via npm i -g @bazel/bazelisk you can from now on run it just using bazel, too.
• 🎏 Support for --//some/path:incompatible_some_flag incompatible flags was added, which are flags defined by Starlark rules.

v1.3.0 (npm and local mirrors)

This fresh Bazelisk release brings two improvements:

• 👩‍💻 @alexeagle contributed support for uploading Bazelisk to npm. If you're a fan of Node.js, try to install your Bazelisk via npm install -g @bazel/bazelisk. (#114).
• 🏗 @ali5h contributed support for a "local mirror" feature. If you specify the BAZELISK_BASE_URL environment variable, Bazelisk will download binaries from that server. We'll iterate on this in the near future to make Bazelisk fully offline and "internal mirror" ready. (#107)

v1.2.1

This patch release fixes a bug that was introduced in v1.2.0. The Bazel version in which an incompatible flag is going to be flipped is now correct.

v1.2.0

Another release with two new features and some bug fixes.

What's new

Go version

• Bazelisk now supports WORKSPACE.bazel files which can be used as aliases for WORKSPACE files.
• The --migrate flag will now print more information about incompatible flags, including the Bazel release in which they will be flipped, and links to their GitHub issues.

Python version

• @clintharrison fixed a bug related to file paths (thank you!).

v1.1.0 (Local Binaries)

This release just adds one feature:

Bazel versions (e.g. in USE_BAZEL_VERSION or .bazelversion) can now refer to absolute paths on the filesystem. As an added convenience, a tilde prefix is expanded to the user's home directory.

Example:

$ USE_BAZEL_VERSION="~/bin/bazel-1.0" bazelisk

This would tell Bazelisk to not download any binaries and instead just directly use the Bazel binary in $HOME/bin/bazel-1.0.

The build process was also updated to use Bazel 1.0 and the latest rules_go version (which means we now build Bazelisk with Go 1.13).

v1.0 (🚀 Enterprise Ready)

Here's another handcrafted Bazelisk release for you, including a few new features and a little bug fix.

Remember: If Bazelisk doesn't yet do what you need it to do, please file an issue or send a PR. 😊

👷 What's new 👷‍♀

• 💖 From now on, we will use semantic versioning, so in case we change environment variable names or how we parse their values in a backwards incompatible way, we'll bump the major version to signal this.
• 🍴 @borkaehw contributed support for using a Bazel fork instead of Bazel's official releases. If you forked Bazel and create your own releases for it on GitHub, just prefix the version with your username / organization name and it'll magically work (e.g. USE_BAZEL_VERSION=philwo/latest).
• ✨ @keith contributed support for the BAZELISK_CLEAN environment flag. If you specify it, Bazelisk will clean run bazel clean --expunge between builds when using --migrate._
• ♻️ @meteorcloudy contributed support for the BAZELISK_SHUTDOWN environment flag. If you specify it, Bazelisk will shutdown Bazel via bazel shutdown between builds when using --migrate. This can help with issues like bazelbuild/bazel#9104.
• 💣 @borkaehw fixed a bug where Bazelisk would crash when your .bazelversion file was empty.