Skip to content

refactor(pypi): migrate requirements.txt lockfiles to uv.lock - #4379

Draft
rickeylev wants to merge 1 commit into
bazel-contrib:use_uv_lock_rulefrom
rickeylev:migrate_to_uv_lock
Draft

rickeylev wants to merge 1 commit into
bazel-contrib:use_uv_lock_rulefrom
rickeylev:migrate_to_uv_lock

Conversation

@rickeylev

Copy link
Copy Markdown
Collaborator

Maintaining platform- and version-specific requirements.txt files
alongside uv.lock duplicated lockfile targets across MODULE.bazel
and WORKSPACE builds.

With uv_lock available in WORKSPACE (#4374), replace the remaining
uv-generated requirements.txt lockfiles in dev, tools/publish,
examples, and tests/multi_pypi with unified uv.lock files loaded
via pip.parse(uv_lock = ...) in MODULE.bazel and uv_lock() in
WORKSPACE.

Replace platform- and version-specific requirements.txt lockfiles in
dev, tools/publish, examples, and tests/multi_pypi with unified uv.lock
files loaded via pip.parse(uv_lock = ...) in MODULE.bazel and uv_lock()
in WORKSPACE.
@rickeylev

Copy link
Copy Markdown
Collaborator Author

AI Disclosure

  • Oversight level: semi-autonomous — This PR was created by an AI coding agent under the direction and review of @rickeylev.
  • Comment handling: Review comments and questions on this PR are monitored by @rickeylev, who either responds directly or directs and reviews agent-assisted updates before they are posted.

This is an automatically generated agent comment.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant