docs(contributing): mention uv lock target for generated lock files (#4411) The generated files guide in `CONTRIBUTING.md` only referenced `compile_pip_requirements`, omitting the `uv` `lock` rule used for dev and docs dependencies. Update the requirements lock files guidance to mention `lock` and its `.update` target alongside `compile_pip_requirements`.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index e035967..0bc85c1 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md
@@ -274,9 +274,10 @@ Some checked-in files are generated and need to be updated when a new PR is merged: -* **requirements lock files**: These are usually generated by a - `compile_pip_requirements` update target, which is usually in the same directory. - e.g. `bazel run //dev:requirements.update` +* **requirements lock files**: These are usually generated by a `lock` (or + `compile_pip_requirements`) `.update` target, which is usually in the same + directory, e.g. `bazel run //dev:uv_lock.update` or + `bazel run //dev:requirements.update`. ## Binary artifacts