| commit | 1f9e46f088225635e8522fd4785766d544751d57 | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Tue Dec 09 22:14:08 2025 +0100 |
| committer | GitHub <noreply@github.com> | Tue Dec 09 21:14:08 2025 +0000 |
| tree | c5879f018cc3d3d9e74f29336ca89c9849db6c7a | |
| parent | bf42b9cbd3f351ce48627bf0c4387c61ec8b2e2a [diff] |
[8.5.0] Inject repositories after root module file processed (#27904)
This fixes an issue where repositories injected with
`--inject_repository` can invalidate `MODULE.bazel.lock` by changing the
order innate `use_repo_rule` extensions are registered.
For example;
```starlark
# //:MODULE.bazel
local_repository = use_repo_rule("@//:defs.bzl", "local_repository")
local_repository(name = "repo")
```
```shell
bazel mod dump_repo_mapping '' --inject_repository=my_repo=%workspace%/other_repo
# Bazel 9+
# {"my_repo":"+local_repository+my_repo","repo":"+local_repository2+repo",...}
# Bazel 8
# {"my_repo":"+_repo_rules+my_repo","repo":"+_repo_rules2+repo",...}
```
Handling repository injections later changes how collisions with
apparent repository names from innate extensions
(`use_repo_rule(...)(...)`) and module extensions
(`use_extension(...).__(...)`) are reported. To permit debugging (and
improve collision investigation in general) the error message now refers
to the incoming and existing repo name definition.
For example;
```diff
-Error in use_repo: The repo name 'my_repo' is already being used by --inject_repository at <builtin>
+ERROR: The repo name 'my_repo' cannot be defined by --inject_repository at <builtin> as it is already defined by a use_repo() call at /___/MODULE.bazel:2:9
```
Closes #27795.
PiperOrigin-RevId: 841889374
Change-Id: I01a4500ae5580338f96d593323c1d680fdbb7672
Commit
https://github.com/bazelbuild/bazel/commit/d564fc98a07af395463ba07ddc6ae5de884e39d2
---------
Co-authored-by: Jordan Mele <mele@canva.com>
Co-authored-by: Yun Peng <pcloudy@google.com>
Co-authored-by: Fabian Meumertzheim <fabian@meumertzhe.im>{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
