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.

v0.0.8

This release fixes a wrong Go import path in the Bazelisk code that was still pointing to the old repository location, which was reported in #70.

It is functionally identical to v0.0.7.

v0.0.7

Here's another exciting Bazelisk release with a fresh set of features for you :)

• Bazelisk now supports the last_rc value for USE_BAZEL_VERSION. This will automatically use the latest available Bazel release candidate if one is available, otherwise it will use the latest stable release. We recommend to use this if you're a Bazel developer so that the release candidates get some real world testing outside of CI, too! (Thanks @fweikert!)
• When asking the GitHub API for available Bazel versions, Bazelisk can now use a GitHub API token so that you don't run into rate-limiting. Simply set the BAZELISK_GITHUB_TOKEN environment variable to a valid GitHub token. (Thanks @keith!)
• Bazelisk now prepends its own version information when you run bazel version. This makes it easier to find out whether you're using Bazelisk and which version of it. (Thanks @zegl!)
• You can now disable the behavior that Bazelisk tries to delegate execution to a <workspace>/tools/bazel script, by setting the BAZELISK_SKIP_WRAPPER environment variable to any value except the empty string. See #61 for an example where this is useful.
• Bazelisk now correctly joins paths on Windows, which should prevent some errors on that platform. (Thanks @excitoon!)

Hope you like it and let us know if there's any issue or feature request we should work on for the next version!

v0.0.6

Please use v0.0.7 instead - this version misses one commit that was intended to be included. 😊

v0.0.5

Fixed searching of workspace on Windows. (#56)

v0.0.4

Supports last_downstream_green Bazel version identifier.

v0.0.3

Improved support for release candidates and incompatible flags.

v0.0.2

This release fixes some small bugs in the previous release 0.0.1

Initial release of Bazelisk in Go

Initial release of Bazelisk in Go