| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
We previously updated to 1.0.0rc2 which isn't released yet to
avoid a security issue. The security issue has been cherry-picked
back to 0.29 and released in 0.29.1:
https://github.com/bazelbuild/bazel/commit/1b771ec1fc8f859c64c3c14a57c53bf0aa2ecb51
Since 0.29.1 is released, update our requirement to that, so that
people can continue to use released things.
Change-Id: Ib48fdbb61bc94a5e78e81e485a5e1d550445a5a5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Given this severe security vulnerability in Bazel 0.29: [1] we prefer
to upgrade to 1.0.0rc2, even though it is a release candidate and not
officially released Bazel version.
This effectively forces users to either download this release
candidate manually from this loation: [2], or use bazelisk if they are
not already, since this RC version is not included in regular package
managers yet.
[1] https://github.com/bazelbuild/bazel/issues/9327
[2] https://releases.bazel.build/1.0.0/rc2/index.html
Change-Id: I7d4121a145450f0d8687b239db3afa14f2dc0785
|
|
|
|
|
|
| |
Also harmonize the version used for Bazelisk to the same version.
Change-Id: I0bbf45fab96346e922c3758ba4e190c21e9440b6
|
|
|
|
|
|
| |
Also harmonize the version used for Bazelisk to the same version.
Change-Id: I084a4b260e2731b28aef3da37aa815bd06bf6a8d
|
|
Bazelisk is utility to switch to the right Bazel version, that we
used to have with Buck build tool: [1].
Bazelisk will download the right Bazel version only once and will use
it in subsequent calls:
$ bazelisk build :release
2019/05/30 16:22:15 Downloading \
https://releases.bazel.build/0.26.0/release/bazel-0.26.0-linux-x86_64...
Bazelisk is storing the binaries in user's cache directory: [2], e.g.
on Linux OS:
$ ls -1 ~/.cache/bazelisk/bin
bazel-0.26.0-linux-x86_64
bazel-0.26.0rc8-linux-x86_64
* [1] https://github.com/bazelbuild/bazelisk
* [2] https://golang.org/pkg/os/#UserCacheDir
Change-Id: I5a4b57f07b59224837c7c66a4fcc8d24425cfac6
|