| commit | a7b1d3662e63a180f5d8d9b9188eac2aa486d02d | [log] [tgz] |
|---|---|---|
| author | Yun Peng <pcloudy@google.com> | Wed Nov 08 09:09:59 2023 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 08 09:11:52 2023 -0800 |
| tree | 4a6a78f20044ad58790154f0517916c467df34be | |
| parent | ba61ff7d2eb6ed697e12abe3688992e85c434b30 [diff] |
Enforce lockfile update - Upgraded rules_python to 0.26.0 to include https://github.com/bazelbuild/rules_python/pull/1433 - Updated the lockfile on all supported platforms. - Enable `--lockfile_mode=update` for regular builds (mostly affecting local build) - Enable `--lockfile_mode=error` for CI builds to ensure lockfile is up-to-date. After this change, please make sure to update the lockfile by running `bazel mod deps` whenever you change the MODULE.bazel file or any .bzl file used in it. Closes #20101. PiperOrigin-RevId: 580553351 Change-Id: I54c3298e6c23c8392226e1e32ba203689f334226
{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
