A user-friendly launcher for Bazel.
APACHE-2.0 License
Bot releases are hidden (Show)
Published by philwo almost 4 years ago
This Bazelisk release contains the following changes:
last_rc
did not work. (#189)Published by philwo about 4 years ago
This Bazelisk release contains the following changes:
Published by philwo about 4 years ago
This Bazelisk release contains the following changes:
Published by philwo about 4 years ago
This Bazelisk release contains the following changes:
Published by philwo about 4 years ago
This Bazelisk release contains the following changes:
Thanks @fwe for the contributions!
Published by philwo about 4 years ago
This Bazelisk release fixes two reported bugs:
tools/bazel
is a directory by ignoring it instead of crashing. (#148)Thanks @Kiougar and @coeuvre for the contributions!
Published by philwo about 4 years ago
This Bazelisk release brings two improvements:
$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! (https://github.com/bazelbuild/bazelisk/issues/111).bazeliskrc
file. Thanks @zellyn! Docs for this feature are here: https://github.com/bazelbuild/bazelisk#bazeliskrc-configuration-file (https://github.com/bazelbuild/bazelisk/pull/127)Known issues:
Published by philwo over 4 years ago
This Bazelisk release contains a feature that improve reliability:
Published by philwo over 4 years ago
This fresh Bazelisk release brings two improvements:
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.--//some/path:incompatible_some_flag
incompatible flags was added, which are flags defined by Starlark rules.Published by philwo over 4 years ago
This fresh Bazelisk release brings two improvements:
npm install -g @bazel/bazelisk
. (#114).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)Published by fweikert almost 5 years ago
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.
Published by fweikert almost 5 years ago
Another release with two new features and some bug fixes.
WORKSPACE.bazel
files which can be used as aliases for WORKSPACE
files.--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.Published by philwo about 5 years ago
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).
Published by philwo about 5 years ago
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. 😊
USE_BAZEL_VERSION=philwo/latest
).BAZELISK_CLEAN
environment flag. If you specify it, Bazelisk will clean run bazel clean --expunge
between builds when using --migrate
._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 https://github.com/bazelbuild/bazel/issues/9104..bazelversion
file was empty.Published by philwo over 5 years ago
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 https://github.com/bazelbuild/bazelisk/issues/70.
It is functionally identical to v0.0.7.
Published by philwo over 5 years ago
Here's another exciting Bazelisk release with a fresh set of features for you :)
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!)bazel version
. This makes it easier to find out whether you're using Bazelisk and which version of it. (Thanks @zegl!)<workspace>/tools/bazel
script, by setting the BAZELISK_SKIP_WRAPPER environment variable to any value except the empty string. See https://github.com/bazelbuild/bazelisk/issues/61 for an example where this is useful.Hope you like it and let us know if there's any issue or feature request we should work on for the next version!
Published by philwo over 5 years ago
Please use v0.0.7 instead - this version misses one commit that was intended to be included. 😊
Published by fweikert over 5 years ago
Published by fweikert over 5 years ago
Supports last_downstream_green Bazel version identifier.
Published by fweikert over 5 years ago
Improved support for release candidates and incompatible flags.