| commit | 067ce4dd8fbcb3dfc02bfdbd82d300befce684ef | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Thu Oct 10 22:24:39 2024 +0200 |
| committer | GitHub <noreply@github.com> | Thu Oct 10 20:24:39 2024 +0000 |
| tree | d10e95e7656a3533d907b4604a4b134f33eb474f | |
| parent | 56dd4765ee6fde3f1575a55488a26269026480a5 [diff] |
[7.4.0] Add `override_repo` and `inject_repo` (#23938) Work towards https://github.com/bazelbuild/bazel/issues/19301 Fixes https://github.com/bazelbuild/bazel/issues/23580 RELNOTES: `override_repo` and `inject_repo` can be used to override and inject repos in module extensions. Closes https://github.com/bazelbuild/bazel/pull/23534. PiperOrigin-RevId: 678139661 Change-Id: Iea7caca949c00e701f056c1037e273fee9740e93 (cherry picked from commit https://github.com/bazelbuild/bazel/commit/46341b1a59c7a1cc8ca0dc604ad53b6de7fee653) Fixes #23724 Fixes #23799 Also includes: * Disallow importing injected repos (8472c9df4d24fe5a54079fe302fe455bccf6930d) --------- Co-authored-by: Xùdōng Yáng <wyverald@gmail.com>
{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
