| commit | 8a44eb04a4b3d4286f126d025a9837247bc2eaa4 | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <ci.bazel@gmail.com> | Tue Jan 06 23:47:14 2026 +0100 |
| committer | GitHub <noreply@github.com> | Tue Jan 06 22:47:14 2026 +0000 |
| tree | 499fdb374dc101ba760d69d3286607a6db9bbc12 | |
| parent | 373ece7d26919007707fdc2593575b16a355d1ba [diff] |
[8.6.0] Partially revert "Make download cache entries read-only" (#28162) This reverts commit 65fe46347318c30df4b9e49827d4439afa8349a7. Breaks repo rules that hit a download cache entry and subsequently attempt to overwrite the file (e.g. http_archive's handling of remote module files). Keeps the added test as it doesn't depend on the change. Work towards #28031 Closes #28148. PiperOrigin-RevId: 852373210 Change-Id: I9e5e9ae87696068fbcb41cfd4dc77c36fea8248b Commit https://github.com/bazelbuild/bazel/commit/d5dba3f70370abd3f875e412e49c807bfc6bedb0 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
