| commit | 89204a10bc1cafd5b2f0af3cf67da1f0752afae2 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Thu Dec 12 01:30:15 2024 +0000 |
| committer | keertk <keerthanakumar@google.com> | Thu Dec 12 01:30:15 2024 +0000 |
| tree | 67067543e7ff3022d295a3f911854332298f8215 | |
| parent | 6155a782d4beccc0c26fbbacc5491c0170fe9daf [diff] |
Release 9.0.0-pre.20241205.2 (2024-12-12)
Baseline: 41557184fedc704037897226f8d255dda0780c55
Cherry picks:
+ a1d1902e07adaad8be3d46a44fa42b2e9b150c1a:
Fix `EmptyRuleConfiguredTargetFactory` for native rules that are
not instances of `EmptyRule`
Incompatible changes:
- The legacy `@bazel_tools//tools/build_defs/repo:maven_rules.bzl`
rule for downloading Maven artifacts has been deleted. Consider
migrating to rules_jvm_external if you are using this rule.
Important changes:
- Fix starlark_doc_extract proto output for symbolic macro
visibility,
attribute inheritance, and rule finalizers; and remove
non-existent "name"
attribute from starlark_doc_extract output for aspects.
- Java tests are no longer run with a `SecurityManager` that
prevents `System.exit`, since `SecurityManager` functionality is
being removed from the JDK.
This release contains contributions from many people at Google, as well as Fabian Meumertzheim, Keith Lea, Keith Smiley, Lucas Loffel, Sara Adams, Xdng Yng.
{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
