| commit | 283ed362e6ccceb047553c2517a0331afd02db90 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Mon Jul 31 16:09:22 2023 +0000 |
| committer | Hee Cha <heec@google.com> | Mon Jul 31 16:09:22 2023 +0000 |
| tree | 0056f29e54f513bd3a4daa1d58a893de24997cf5 | |
| parent | 5de5d3b68f293815d5cc736f8f8e59f9794d31df [diff] |
Release 6.3.1 (2023-07-31) Baseline: 0f231ac8acabcd8aa309da041c98ab90a1552418 Release Notes: + Mark isolated extension usages as experimental (#19050) + Fix a bug where frozen targets list was mutated while expanding env attribute (#19052) + Add documentation for --experimental_isolated_extension_usage (#19071) + Advertise CcInfo from cc_import (#19086) + Create .bazelversion to address postsubmit issues (#19089) + Update java_tools version to 12.6 (#19091) + Disable lockfiles by default (#19106) Acknowledgements: This release contains contributions from many people at Google, as well as Brentley Jones, Fabian Meumertzheim, oquenchil, Xùdōng Yáng.
{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
