Skip to content

Releases: bazelbuild/bazelisk

v1.17.0

16 May 14:09
70e3e87
Compare
Choose a tag to compare

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!

v1.16.0

02 Feb 21:16
fc3e3d6
Compare
Choose a tag to compare

Bazelisk v1.16.0 comes with updated dependencies, minor bug fixes and some improvements:

The Go version...

  • ... no longer causes 'file name too long' errors on MacOS (#396),
  • ... works correctly when no GitHub token is specified (#412),
  • ... now supports tools/bazel.ps1 and tools/bazel.bat on Windows (#417).

The Python version now works on Linux arm64 machines (#397).

We’d like to thank our amazing contributors @bduffany, @chenrui333, @gregmagolan, @rpwoodbu, @sudowork and @UebelAndre !

v1.15.0

04 Nov 18:56
c908174
Compare
Choose a tag to compare

v1.15.0 comes with several notable changes to the Go version of Bazelisk:

  • Features:
    • Added support for users-specific .bazeliskrc files, in addition to .bazeliskrc files in the workspace root (#390).
  • Fixes:
    • Fixed an issue where Bazelisk ignored the tools/bazel wrapper (#345).
    • Startup options are now correctly passed to bazel clean and bazel shutdown, thus ensuring that the commands affect the correct Bazel server (#362).
    • Suppressed incorrect fallback warnings on Apple Silicon when fetching Bazel binaries built at specific commits (#392).

We’d like to thank our amazing contributors @JaredNeil, @jbms, @LINKIWI, @meteorcloudy and @Vertexwahn!

v1.14.0

08 Sep 15:07
4dd53d9
Compare
Choose a tag to compare

This release brings two small improvements:

  • On Linux, Bazelisk now downloads Bazel binaries built on CentOS 7, thus ensuring compatibility with older Ubuntu versions such as 14.04 and 16.04.
  • Everyone who uses Bazelisk as a library can now dynamically compute Bazel flags based on the resolved Bazel version. (#358). Thank you @tjgq!

v1.13.2

06 Sep 13:06
cc9d95a
Compare
Choose a tag to compare

This release fixes performance issues when using floating version identifiers (e.g. "5.x").

We'd like to thank @chenrui333 for their contributions to this release.

v1.13.1

05 Sep 12:31
5387890
Compare
Choose a tag to compare

This patch release fixes "go build" / "go get" of Bazelisk. Unfortunately v1.13.0 could only be built with Bazel.

v1.13.0

02 Sep 16:11
48e743d
Compare
Choose a tag to compare

This release makes it easier to run Bazel with incompatible flags by introducing the BAZELISK_INCOMPATIBLE_FLAGS environment variable (#349).

It also contains some minor maintenance / cleanup changes.

v1.12.2

17 Aug 12:40
da51894
Compare
Choose a tag to compare

This is a patch release that improves error messages wrt unsupported arm64 platforms.

v1.12.1

16 Aug 15:51
89dc94c
Compare
Choose a tag to compare

This is a patch release for v1.12.0 which fixes the 404 download errors on Linux (#346).

It also introduces custom fallback behavior (#289) and fixes the handling of SIGINT (#322).

We'd like to thank our contributors @bb010g and @gibfahn.

v1.12.0

15 Jun 17:16
40d8ae3
Compare
Choose a tag to compare

This release brings new features and fixes to both versions of Bazelisk:

Go:

  • Added support for basic HTTP authentication via a .netrc file (#292)
  • Improved and fixed Apple Silicon support (#299, #303)
  • Rolling releases are now fetched from GCS instead of GitHub (#319)

Python:

  • Added support for Apple Silicon (#272)
  • Implemented verification of downloaded Bazel binaries (#295)

We'd like to thank our contributors @chenrui333, @codeman9, @cpsauer, @keith, @linzhp, @Warchant and @xinnjie!