v1.24.1

Bazelisk v1.24.1 is a patch release with some minor fixes:

Bug Fixes & Improvements

• bisect now accepts Bazel release branch names (#633).
• Improved error message when LTS binaries are missing (#639).
• Fixed a performance regression caused by too many unnecessary HTTP requests, which was introduced in v1.24.0 (#641).

We’d like to thank our amazing users & contributors!

v1.24.0

Bazelisk v1.24.0 comes with a new feature:

New Features (Go)

• Implemented support for a new wildcard version identifier: Users may now specify a version like 7.* that refers to the latest release or candidate from the given LTS track. Please note that this is different from the existing 7.x identifier which only matches releases, but not candidates (#636).

We’d like to thank our amazing users & contributors!

Known issue: #640

v1.23.0

Bazelisk v1.23.0 comes with several improvements related to downloads:

Bug Fixes & Improvements

• Improved download error messages (#624)
• Fixed INTERNAL_ERROR problems caused by improper handling of HTTP responses during retries (#627)

We’d like to thank our amazing contributors @jjmaestro and @jwnimmer-tri!

v1.22.1

Bazelisk v1.22.1 is a patch release with the following changes:

Bug Fixes & Improvements

• Multiple instances of Bazelisk can now run concurrently without causing problems (#616).

We’d like to thank our amazing contributor @sushain97!

v1.22.0

Bazelisk v1.22.0 comes with several significant changes:

New Features (Go)

• Bazelisk sets the BAZELISK env variable so that scripts can detect whether they're running under Bazelisk (#612)
• --bisect now supports finding the first fixing commit by prefixing the range with ~ (#613)

Removed Features (Go)

• Removed support for last_downstream_green since the downstream pipeline stopped producing green commits some time ago.

Bug Fixes & Improvements

• Improved last_green support (#614)

We’d like to thank our amazing contributors @fmeum and @jwnimmer-tri!

v1.21.0

Bazelisk v1.21.0 comes with several significant changes:

New Features (Go)

• Users can set an OS-specific Bazelisk home directory, e.g. via BAZELISK_HOME_WINDOWS (#474)
• BAZELISK_WRAPPER_DIRECTORY allows users to specify paths other than the default tools/bazel location (#567)
• BAZELISK_HOME: Environment variables as well as the tilde sign are now properly expanded (#587)
• Bazelisk can fetch Linux ARM64 Bazel binaries built for commits (#604)

Bug Fixes & Improvements

• The Python version properly handles empty lines in .bazelversion files (#576)

We’d like to thank our amazing contributors @albertocavalcante, @API92, @jwnimmer-tri, @keith and @mzapotoczny!

v1.20.0

Bazelisk v1.20.0 comes with several significant changes:

New Features

• The Go version now supports BAZELISK_NOJDK (#531)

Bug Fixes & Improvements

• It's now easier to use Bazelisk programmatically (#500, #526)
• Bazelisk will retry more connection errors (#529, #530)
• A display bug in the download progress bar has been fixed (#539)

We’d like to thank our amazing contributors @afq984, @comius, @francine-blanc, @illicitonion, @jwnimmer-tri, @LINKIWI, @mmorel-35 and @sf-jbazuzi!

v1.19.0

Bazelisk v1.19.0 comes with two significant changes:

• MODULE.bazel and REPO.bazel files are now obeyed (#503)
• Users will see a progress bar during binary downloads (#511)

We’d like to thank our amazing contributors @crncnnr and @katre!

v1.18.0

Bazelisk v1.18.0 contains some bug fixes and internal cleanups. Most notably, it uses consistent Bazel paths to avoid spurious rebuilds when downloading the same Bazel binary from a different mirror (#465).

We’d like to thank our amazing contributors @alexeagle, @fmeum, @illicitonion, @sluongng and @wisechengyi!

v1.17.0

Bazelisk v1.17.0 comes with updated dependencies, minor bug fixes and new features:

The Go version...

• ... supports custom download URLs via the BAZELISK_FORMAT_URL env variable (#427)
• ... now only downloads Bazel when necessary (#438)
• ... can check the hash of downloaded binaries via the BAZELISK_VERIFY_SHA256 env variable (#441)
• ... makes it easier to find out which Bazel change broke your build with the --bisect option (#451)
• ... is more robust in the face of transient GCS download issues (#459)

The Python version now properly recognises WORKSPACE.bazel files (#443).

We’d like to thank our amazing contributors @jmmv and @jwnimmer-tri!