| commit | 7d4b8a559c59339f6916f1aa6358132194842537 | [log] [tgz] |
|---|---|---|
| author | Ignas Anikevicius <240938+aignas@users.noreply.github.com> | Fri Oct 25 11:46:08 2024 +0900 |
| committer | GitHub <noreply@github.com> | Fri Oct 25 02:46:08 2024 +0000 |
| tree | 5054474db564da25ab75da65752f363801aebbf6 | |
| parent | c7a20785bd158f04680be0b7270c76cf6fe4b4cb [diff] |
chore: bump twine dependencies and cleanup for 1.0 (#2333) This change updates the `requirements.txt` for all of the platforms for the `twine` component that is used in wheel publishing rules. Before that the deps would be maintained by `dependabot.txt` and it seems that it would constantly exclude the `requirements.txt` from the updated files, this means that the `requirements.txt` (used on Linux) has gone out of sync and it would be better to use a different mechanism to keep them in sync. Hence the proposal is to: - Use `uv` to sync the requirements. - Add `requirements_linux.txt` to explicitly highlight that the file is for Linux. - Keep `requirements.txt` but note that it is deprecated. - Add `requirements_universal.txt` in case people want to use a single requirements file. - Bump the dependencies to the latest versions and bring them back in sync. Whilst at it I had to: - support extra parameters in the locking format and allow setting visibility - chore: add `rules_multirun` as a `dev_dependency` - refactor: `uv pip compile` requirements for tools/publish - chore: bump uv to 0.4.25
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.