Skip to content

Conversation

aignas
Copy link
Collaborator

@aignas aignas commented Oct 23, 2024

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

@aignas aignas requested a review from rickeylev as a code owner October 23, 2024 08:45
@rickeylev
Copy link
Collaborator

feat: support extra parameters in the locking format and allow setting visibility

This is just for the uv backed one, right? Which is still private. My point being: it shouldn't be in the changelog, since it's just a private thing we use for ourselves.

CI has some failures, I think its just missing WORKSPACE equivalent updates.

@aignas aignas requested a review from groodt as a code owner October 24, 2024 00:43
@aignas aignas enabled auto-merge October 25, 2024 02:35
@aignas aignas added this pull request to the merge queue Oct 25, 2024
Merged via the queue into bazel-contrib:main with commit 7d4b8a5 Oct 25, 2024
4 checks passed
@aignas aignas deleted the chore/cleanup-publish-requirements branch October 25, 2024 09:46
github-merge-queue bot pushed a commit that referenced this pull request Oct 25, 2024
This got accidentally committed in #2333.
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.

2 participants