| commit | 34387472ea6d006ddaf40ef450cd726b915f85b8 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Feb 11 13:54:01 2022 +0100 |
| committer | fweikert <fwe@google.com> | Fri Feb 11 13:54:01 2022 +0100 |
| tree | 5c5486c44229c1cf5ccf64925922e8b649cab6f1 | |
| parent | 27b3cb1e8cff8425d167c95843a698e9fd7cbeba [diff] |
Release 6.0.0-pre.20220201.3 (2022-02-11)
Baseline: c7652d875869ec063addd146a2746c1378c73236
Cherry picks:
+ 1c0cf8ee505edee539ebb1ce84a78da8e6064d0a:
Undelete BigIntegerCodec deleted in
https://github.com/bazelbuild/bazel/commit/16753d6ab16c22ed8cfd42
47e05c695223b67616. Belatedly realized needed for Starlark
bigint serialization.
+ 382b187d4df664e555608c895716172d96e092c5:
Automated rollback of commit
9998c6361d3d7c22184ea07e363f38e88a345701.
+ 45ce5459f3a8f0a32ec71c13c22500ba87aaa8c2:
Rollback
https://github.com/bazelbuild/bazel/commit/8174262bf946e31df86476
014c6f231f46ca0882
This release contains contributions from many people at Google, as well as Denys Kurylenko, Keith Smiley.
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
Follow our tutorials:
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
