| commit | 45982b4040096bdd76329c7034d72f2bae673e4e | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Wed Apr 24 21:58:10 2024 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Apr 24 21:59:51 2024 -0700 |
| tree | bb60b1f89041fdc7c14e2292caf3924f05e3ce61 | |
| parent | 1ff310b89da8c2050f12178fa9c8b57165afe1f0 [diff] |
Revert special handling of yanked module files This effectively reverts most of 2a2a4743ad624f7f238b7771b8ceedb7649e8f5c: Module files of yanked versions are evaluated just like those of any other versions and "yankedness" is only checked for the final dep graph after selection. This greatly simplifies incremental fetching of (inherently mutable) yanked version information with the new lockfile format. Work towards #20369 RELNOTES: `print` statements in module files are now only executed for the root module and modules subject to non-registry overrides (e.g. `local_path_override`). Closes #22083. PiperOrigin-RevId: 627953972 Change-Id: Ie0aba02d187e000450a89ad2cd281c173582880a
{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
