| commit | 3ae91caffbbc9a694b439b03a116bcd1ce293bb3 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Mon Nov 11 06:42:24 2024 +0000 |
| committer | keertk <keerthanakumar@google.com> | Mon Nov 11 06:42:24 2024 +0000 |
| tree | ed63eef8be20fcf42d0046df24126d280fd0dabe | |
| parent | dcf80a0d37e3b1c75f81669fc3419be450d2c489 [diff] |
Release 9.0.0-pre.20241105.2 (2024-11-11)
Baseline: dcf80a0d37e3b1c75f81669fc3419be450d2c489
Incompatible changes:
- On Windows, a change to the output base locking protocol might
cause an older Bazel invoked immediately after a newer Bazel (on
the same output base) to error out instead of blocking for the
lock, even if --block_for_lock is enabled.
Important changes:
- A no-config transition is now available as `config.no_config()`.
- Actions that create runfiles trees are now considered regular
actions. This means that they are now reported in statistics,
critical paths and the like.
- External repositories that are managed by Bzlmod can now contain
a top-level `external` directory or package.
This release contains contributions from many people at Google, as well as Alexander Golovlev, Fabian Meumertzheim, Farid Zakaria, Honnix, Jay Conrod, Keith Smiley, Matt Brown, Roman Salvador.
{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
