| commit | f231358115c8d411a77b7e5b0a7a7dd6867679fd | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <rlevasseur@google.com> | Thu Oct 24 10:55:33 2024 -0700 |
| committer | GitHub <noreply@github.com> | Thu Oct 24 17:55:33 2024 +0000 |
| tree | f72420b64d291c9e899eaffa18771814bfc6686f | |
| parent | 6babe59e991f1b8a7279c78a2b536980db6f6eb3 [diff] |
deps: use rules_cc 0.0.13 to support newer bazel versions (#2335) In order for WORKSPACE to work with newer bazel versions, rules_cc 0.0.13 or higher is necessary. rules_cc then requires a newer protobuf version. Note I couldn't figure out the minimum protobuf version, but 27.0 seems to work OK. AFAIK only WORKSPACE is affected. Our bzlmod uses 0.0.9 and hasn't had issues. Fixes https://github.com/bazelbuild/rules_python/issues/2310
This repository is the home of the core Python rules -- py_library, py_binary, py_test, py_proto_library, and related symbols that provide the basis for Python support in Bazel. It also contains package installation rules for integrating with PyPI and other indices.
Documentation for rules_python is at https://rules-python.readthedocs.io and in the Bazel Build Encyclopedia.
Examples live in the examples directory.
The core rules are stable. Their implementation is subject to Bazel's backward compatibility policy. This repository aims to follow semantic versioning.
The Bazel community maintains this repository. Neither Google nor the Bazel team provides support for the code. However, this repository is part of the test suite used to vet new Bazel releases. See How to contribute page for information on our development workflow.
For detailed documentation, see https://rules-python.readthedocs.io
See Bzlmod support for more details.