| commit | b9ec06fc498f8b01a9779120100cc009a2c83b33 | [log] [tgz] |
|---|---|---|
| author | Richard Levasseur <richardlev@gmail.com> | Thu Oct 16 16:16:49 2025 -0700 |
| committer | GitHub <noreply@github.com> | Thu Oct 16 16:16:49 2025 -0700 |
| tree | a8d53ac0c858709b84d1b979eee6e16eb68db83d | |
| parent | cd49a1cab10a1953c6228063bbb12948307ba44c [diff] |
chore: switch to use publish-to-bcr workflow (#3359) The GitHub App is deprecated, so switch to the more modern workflow. This will also allow us to eventually use attestations. Along the way... * Split up the release workflow into some different sub-jobs * Run PyPI upload last, as its the most irrevocable step of the process.
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.