| commit | ce48b3a8b2177c6bb84cf880ace53957f4e4ddc7 | [log] [tgz] |
|---|---|---|
| author | Bazel Release System <noreply@google.com> | Fri Jan 16 16:09:33 2026 -0800 |
| committer | Carmen Chui <carmenchui@google.com> | Fri Jan 16 16:09:33 2026 -0800 |
| tree | 5da4330b6b2354ae7b47f159ede236063cfa9816 | |
| parent | 6dd350795aedf2474a35a5cf2496d247c20a827d [diff] |
Release 10.0.0-pre.20260112.1 (2026-01-16)
Baseline: 7111cbfcecdd3bda3e4beedd8b59dc93d3652607
Cherry picks:
+ 76166fca04ca8fdf6d87b3a2a7cf60da6ca8145b:
Use the hermetic python toolchain for Bazel
Important changes:
- The new `package_relative_label` function on the rule context
(`ctx`) can be used to turn a user-provided label string into a
`Label` relative to the target that is currently being analyzed
(where `Label(...)` would return a `Label` relative to the `.bzl`
file containing the call).
This release contains contributions from many people at Google, as well as Alex Eagle, Alex O'Brien, Carmen Chui, Damian Banki, dependabot[bot], Fabian Meumertzheim, George Gensure, google-labs-jules[bot], jade.
{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
