| commit | 6b2b8709820b71b52595b3c7da2ada226eafb869 | [log] [tgz] |
|---|---|---|
| author | bazel.build machine account <15028808+bazel-io@users.noreply.github.com> | Thu Nov 30 15:51:41 2023 -0500 |
| committer | GitHub <noreply@github.com> | Thu Nov 30 20:51:41 2023 +0000 |
| tree | 7960c81d86a6f6c3be90a32671bf7fd34e51f4f2 | |
| parent | 0725711d76f8738be0f57cf210efaea0e0a32742 [diff] |
[7.0.0] Make lockfile extension updates more obviously correct (#20400) * Removes code paths in `BazelLockFileModule` that are never taken now that lockfile update events are replayed by Skyframe. * `BazelModuleResolutionEvent` no longer contains a `BazelLockFileValue` that is internally inconsistent: Previously, this values combined the (potentially updated) extension usages resulting from the resolution with the old locked extension results obtained from the previous state of the lockfile. The logic in `BazelLockFileModule` handled this correctly, but it should now be more obvious that it does so. * No longer parse the lockfile twice, once in `BazelLockFileFunction` and once in `BazelLockFileModule`. Closes #20311. Commit https://github.com/bazelbuild/bazel/commit/1691f60c2ec222a392c8708ddc4cc35a969c4f7c PiperOrigin-RevId: 586744057 Change-Id: Id85dbde627878c18baf3c375a0091a4f989b146b 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
