| commit | 9bf8f396db5c8b204c61b34638ca15ece0328fc0 | [log] [tgz] |
|---|---|---|
| author | Fabian Meumertzheim <fabian@meumertzhe.im> | Fri Sep 29 16:11:40 2023 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Sep 29 16:14:25 2023 -0700 |
| tree | 573461f6c2e7b7f394b678ff3d1838e8a6c22bbc | |
| parent | d6254dc384243722b0a5360ffdcddab41b5c21df [diff] |
Remove stale extension entries from lockfile When changes to module files result in module resolution rerunning, extension results from the lockfile may become stale due to changed usages even if the current build doesn't evaluate the affected extension. We now compare the current usages against the usages recorded in the lockfile and drop all extensions that became stale. Along the way, also trim tag locations when comparing usages for staleness detections as they do not affect the evaluation result. Closes #19658. PiperOrigin-RevId: 569612685 Change-Id: I8e9e30c37076ef2cbfa6e0498b9e003a078e4c67
{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
