Skip to content

docs: Explain why the lock rule has no implicit test target #3411

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 17, 2025
Merged

docs: Explain why the lock rule has no implicit test target #3411

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions python/uv/lock.bzl
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,13 @@ Differences with the legacy {obj}`compile_pip_requirements` rule:
- This does not error out if the output file does not exist yet.
- Supports transitions out of the box.

Note, this does not provide a `test` target, if you would like to add a test
target that always does the locking automatically to ensure that the
Note, this does not provide a test target like {obj}`compile_pip_requirements` does.
The `uv pip compile` command is not hermetic and thus a test based on it would most likely be flaky:
- It may require auth injected into it, so most likely it requires a local tag added so that the bazel action runs without sandboxing.
- It requires network access.

Given those points, a test target should be an explicit and properly documented target and not a hidden implicit target.
If, you would like to add a test target that always does the locking automatically to ensure that the
`requirements.txt` file is up-to-date, add something similar to:

```starlark
Expand Down