| commit | 6ac0ee524419c7c99964c303373bdf32fe90ffe0 | [log] [tgz] |
|---|---|---|
| author | Xdng Yng <wyverald@gmail.com> | Tue Dec 14 03:01:57 2021 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Tue Dec 14 03:03:30 2021 -0800 |
| tree | 63bfe2adba1700ef0fada5a955182050d546a017 | |
| parent | 35a6fc5e4db88dd3370de23e0f370608bc4e2203 [diff] |
Make sure that absolute packages don't go through repo mapping https://github.com/bazelbuild/bazel/commit/103ea9d3f3a0d85a0d7c1ad98fd8dbb422505d95 refactored label parsing, getting rid of the "default" repo name (using "main" instead). This meant that absolute packages such as "//visibility" would now always map to the main repo. This is normally correct, except that this main repo would then go through repo mapping, so if any non-main repo tried to use such labels, they would get a "non-visible" error (with Bzlmod enabled only; otherwise, repo mappings allow fallback). This commit fixes it so that such usages of the main repo don't go through repo mapping at all. Fixes https://github.com/bazelbuild/bazel/issues/14403. Closes #14412. PiperOrigin-RevId: 416252184
{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
